Maply — Property Takeover Accounting (Ameba)

How it works

01

Upload

Drop in the prior firm's trial balance CSV.

02

Assign

Select source rows and choose the Yardi account they belong to — try it below. Many rows can roll into one account, and the balances automatically sum as you go.

03

Review

Review your mappings from step 2.

04

Export

Set the takeover date, property, and book, then download a Yardi-ready journal entry.

Your firm's chart of accounts is uploaded once in Settings and reused on every session.

Try it — no account needed

Assign a row. Watch the number tie-out.

This is the actual Assign step, running on sample data in your browser. Select an unassigned row, click it, and pick the Yardi account it belongs to. Watch the totals update in real-time.

sample data · nothing is saved

Sample takeover — try it yourself

Your Yardi chart of accounts

Unassigned source rows

Built for Takeover

Today

Mapping lives in someone's personal spreadsheet

No record of who approved which mapping, or when

A skipped row doesn't error — it's just missing when the numbers are reviewed weeks later

Redone from scratch for the next building

With Maply

Every mapping is manual and reviewable

Export is physically blocked until source total equals mapped total

Your chart of accounts is uploaded once and reused on every session

You leave with a CSV file that is ready to be uploaded to Yardi

What actually goes wrong

Six ways a rushed takeover costs you later

None of these require bad accounting — just enough rows, and enough pressure to get to zero.

Unmapped rows still carry a balance

A skipped account isn't zero. It's money with nowhere to go, and it won't throw an error — it just won't be there when the trial balance is reviewed.

Many-to-one mappings need a paper trail

When two prior accounts roll into one of yours, someone eventually asks why. "I think that's what we did last time" isn't an answer.

A spreadsheet has no audit trail

Cell formulas don't record who assigned what, or when. If a mapping is ever questioned, there's nothing to point to.

A clean-looking export can still be wrong

A journal entry can import into Yardi without erroring even if the source never tied out. Reconciliation has to happen before export, not after.

Rushed takeovers get rushed exceptions

Go-live dates don't move for a messy chart of accounts. Under pressure, exceptions get "handled later" — and later rarely comes.

One-off mapping doesn't scale

Recreate the same account-by-account decisions for the next ten buildings, or keep the chart of accounts that already answers most of it.

Move a prior firm's financials into your Yardi Chart of Accounts