Bring accounting data in and take it with you

Import with an explicit reconciliation target

PolyAccounts supports bank CSV import and review workflows. Inspect account mapping, dates, amounts, payee coding and potential duplicates before posting reviewed transactions. A CSV upload is not proof that a migration is complete.

Record the source row count, date range and control totals. Compare imported results by account and period, including transfers and split transactions. Keep the original source unchanged.

Read structured accounting data

The hosted agent connection exposes structured ledger entries, financial statements and company context. Monetary outputs use exact decimal strings. Preserve those values using decimal or integer arithmetic rather than converting them through binary floating-point calculations.

For multi-page ledger reads, follow next_cursor with the original company and period filters. Exclude soft-deleted entries from active balances while preserving history where the documented endpoint provides it. Cite record IDs so an accountant can trace an answer back to the books.

Keep an exit path

Use the ledger’s export controls and structured API reads to evaluate whether you can retrieve the records your workflow needs. Verify exported date ranges, account names, transaction IDs, debit and credit values, currency and row counts against the source.

A ledger CSV is not a complete backup of every application object. Check supporting documents, payment history, audit records and relationships separately. Do not assume a direct importer for every competing product, continuous bank-feed availability or lossless round-trip migration without testing your exact format.

Before any real-data cutover

Import real company data into your own workspace. Agree the account mapping, keep the source files and reconcile balances before completing the migration. An agent can assist with evidence gathering, but the company remains responsible for deciding whether the resulting records are suitable.