Evidence and imports

Evidence is what a source said. Keep that distinct from the interpretation of the business and from the journals that affect reported numbers.

Supported inputs

The application accepts PDF, CSV, XLSX, XLS, QBO, OFX, Markdown, plain text, and direct notes. Suitable sources include bank activity, invoices, agreements, spreadsheets, and accounting exports. A supported file format does not guarantee every layout or accounting treatment can be interpreted correctly.

Original files retain hashes and source metadata. Normalized rows and extracted facts provide references back to the evidence. Use readable exports and inspect extraction quality, especially for scanned or irregular documents.

Review an import

1. Select the company that owns the source.
2. Upload the file in the workspace.
3. Review document identity, including the account, reporting currency, entity and statement period when relevant.
4. Inspect extracted facts and their source references. Correct or reject unsupported interpretations.
5. Review account mappings and posting proposals. A proposal still has to pass deterministic posting controls.
6. Inspect posted activity and record the supported account/date coverage.

Approval of evidence, approval of accounting, posting, coverage and balance reconciliation are separate controls. Passing one does not imply all the others passed.

Avoid duplicate financial effects

Do not assume a payment appearing in a bank export, invoice and ledger export is automatically one event. Shared amount or date is not sufficient identity.

Use Import corrections to compare explicitly selected sources. Equal normalized rows can retain their original postings. Changed identifiers may require a one-to-one row mapping; partial updates must not remove transactions that were simply omitted from the new file.

For an actual payment that fulfills a forecast obligation, use Forecasts and actuals instead. Import duplication and forecast settlement are different problems.

Inspect the result

From /progress, inspect a month to see journals, preceding opening entries, expectation history, formulas, decisions and source links. Downloaded source files are company-scoped attachments. Saved reviews retain evidence references and calculation inputs; they do not turn a missing source or an unsupported treatment into verified data.

If the financial effect is wrong, correct the relevant mapping, proposal or journal through its review workflow. Preserve the original evidence and reverse a posted journal when a correction requires it.

What goes to a model

Interpretation uses the configured model provider. Self-hosting the database does not mean model processing is local. Treat source text sent for interpretation according to your own provider and data-handling requirements. Never include credentials in evidence or financial notes.

Continue with Starting cash and coverage or Import corrections.