Software collection playbook

Sage Intacct: entity, document and journal evidence

Entity and financial report/document scope.

By Sam Yang · Updated 2026-10-07

Did the export finish, and which entity did it describe?

For report collection, prove entity, basis and full detail. For a proposed correction, require native document read-back: a collected GL or a staged file cannot establish that a change posted.

Evidence basis: Saved entity/report download and close-review observations. They do not authorize imports or establish every product menu.

Check the exact entity, source objects, permissions and financial report availability.

Top Level and company reports disagree

First align entity and consolidation scope. Do not diagnose an accounting error from differently scoped reports.

An import review shows mixed successful and failed entries

Preserve the result for each document and signed line. A governed retry should target only failed entries, not replay the whole file; this collection guide permits no retry or posting.

Use supported API or native report access for the required scope. A permitted browser session can collect a specific gap. Neither route proves reconciliation or complete costs.

Put the evidence to work

The journal batch balances. Why is the entity close still incomplete?

A balanced batch is an arithmetic control, not a complete entity close. One batch can contain multiple documents, and a consolidated report can cover a different population from an entity report. Preserve the entity, book, currency, document and line before deciding which difference needs correction.

Explain an entity-versus-top-level report difference

Write down the entity, reporting book, period, basis, currency and dimension filters for each report. Do not compare only report titles.
Select and verify the rendered entity. If selection opens another tab, verify that tab rather than continuing in the original top-level view.
Collect completed GL and trial-balance files for aligned scope. Include zero-ending accounts so offsetting period movement remains visible.
Group journal lines by entity and account while retaining journal, document reference and line identity. Compare movements and ending balances.
Classify the difference as scope, currency/consolidation, omitted detail or unexplained accounting evidence. Re-run only the affected collection with corrected scope.

Bring to the review: A scope comparison and an entity-account bridge, with zero-ending movement and excluded populations explicit.

Then decide: Resolve report-scope differences first. A consolidated total does not replace the selected entity's control totals.

Review a mixed posting result without replaying successful documents

Preserve the original submission identifiers and per-document outcome. Keep extracted, proposed, submitted and posted states distinct.
For each document claimed posted, obtain native document or journal read-back and retain every signed line and entity.
For failures, record the specific document, error and live source state. Check whether any lines or dependent documents already exist.
Review document completeness and account/dimension meaning. Do not infer account roles merely from a shared numeric prefix.
Produce a failed-only review set with the independently confirmed successful documents excluded. Any actual retry belongs to the approved accounting workflow.

Bring to the review: A document outcome register with native references, signed lines, errors and a failed-only review set.

Then decide: A reviewer decides what should be corrected or retried. The collection of a fresh GL does not by itself prove that proposed corrections posted.

Which collection route answers this question?

Choose the route for the missing evidence and the access available in your account. The comparison below distinguishes documented coverage from coverage that still needs checking.

Supported API reads

What it supplies: Sage documents journal batches and journal-line queries, including distinct GLBATCH and GLENTRY objects. Sage currently recommends its REST API for client applications while documenting legacy XML functions.
What still needs proof: Exact REST object parity, subscription, permissions and report scope must be checked in the deployed account. Journal access alone does not cover all cash and subledger evidence.

Choose it when: Use supported reads when they retain the required entity, document and line fields.

Native GL and trial-balance files

What it supplies: Saved procedures establish native entity-scoped collection and a generated Download the file link in an observed export flow.
What still needs proof: Clicking CSV does not prove completed delivery. File filters, currency/book and zero-ending-account settings still need verification.

Choose it when: Use native files for report-definition fidelity and control totals, retaining the actual downloaded bytes.

Permitted browser detail

What it supplies: The browser can inspect the selected entity and native document detail or finish an authorized export delivery.
What still needs proof: Frame structure and menu labels are dated observations. Browser collection is not permission to import, post or replay a batch.

Choose it when: Use it to close a specific evidence gap and verify document state when the adequate API or file route is unavailable.

Reproduce the diagnostic

One balanced batch, two documents and a zero-ending account

All records and amounts below are fictional teaching inputs. This example demonstrates the calculation, not a customer outcome or a reproduced software defect.

All four signed lines sum to zero. Clearing account 1090 also sums to 450 - 450 = 0, but contains two movements. Filtering on only nonzero ending accounts would hide this account's movement. DOC-01 and DOC-02 each have two lines even though they share T-01.

What the CSV columns mean

This is fictional teaching data in USD, not a Sage export or a customer posting.
signed_amount uses debits positive and credits negative. document_ref and line_id are independent of batch_id.
Entity A opens at zero on the illustrative clearing account 1090. Two lines on that account move 450 in and out; zero ending balance does not mean no movement.

Batch net: 0 USD; Arithmetic balance only.
Clearing account net: 0 USD; No ending balance change.
Clearing account movements: 2 rows; Two nonzero movements remain relevant.
DOC-01 lines: 2 rows; Retain both signed lines.
DOC-02 lines: 2 rows; A separate economic document in the same batch.

Inspect journal-lines.csv

batch_id,entity,document_ref,line_id,account,signed_amount
T-01,A,DOC-01,L-01,1090,450
T-01,A,DOC-01,L-02,4000,-450
T-01,A,DOC-02,L-03,5000,450
T-01,A,DOC-02,L-04,1090,-450

Download this CSV

Next decision: Use the two document references and four line identities for review. Balanced arithmetic does not establish business purpose, correct classification, posting success or a complete close.

Expected results and calculation checks Download the reproduction code

Run the example locally

Save the CSV files, expected-results.json and reproduce.mjs in one folder. With Node.js installed, run the command below. It calculates the checks from the CSV bytes and rejects a changed input or expected result.

node reproduce.mjs expected-results.json

No software login, customer records or API key is required.

When the result does not make sense

A trial balance agrees overall but account movement seems missing.

Check: Check whether zero-ending accounts were excluded. An account can have debit and credit movement that nets to zero.

Resolve the question: Collect that scope with zero-ending accounts included and retain both movements. Do not use a zero balance as proof of no activity.

The CSV action completed but no usable file arrived.

Check: Check the actual generated file/download link and inspect received bytes, rather than the request screen.

Resolve the question: Finish the authorized delivery or mark it pending. Keep the prior complete export separate from the current unfulfilled request.

A batch shows both successful and failed documents.

Check: Verify each document with its native identity and all lines. A batch-level status can hide different outcomes.

Resolve the question: Give the reviewer a failed-only set. Do not replay the whole batch or label all documents posted from one success message.

Where automation earns its place

Good work for automation

Repeatable entity/filter checks, complete file delivery, line-level footing and per-document exception registers can reduce repeated close work.

Keep a person on these decisions

The accountant interprets consolidation, books, currency and document purpose, then reviews correction and retry decisions. A tool should retain mixed outcomes rather than turn a batch response into a blanket success.

References behind these workflows

Product documentation supports the specific scope stated beside each source. Level's diagnostic methods and fictional calculations remain distinct from vendor capabilities.

Sage journal batches and lines
Distinct journal batch and line objects, signed lines, document and location fields. Reviewed 2026-10-07.
Sage API reference and current REST recommendation
Documented API families and recommendation to use REST for client applications; entitlement is account-specific. Reviewed 2026-10-07.

Explore the financial diagnostic examples

Collect and verify the population

General Ledger and Trial Balance: Use the same entity, period and basis; include zero-ending accounts so movement is not omitted.
CSV delivery: Follow a generated Download the file link when present and retain the completed native bytes, not only the request screen.
Native document and split lines: Keep posted date, journal, transaction and document reference distinct. One batch can contain multiple economic documents.

Use native GL/TB/report export filters and actual download links; retain entity, date, basis, report population and document identifiers. Verify applications and native read-back separately from GL collection.

Dated collection sequence

Dated saved collection procedure reviewed October 6, 2026. Verify the current account, interface, permission and available reports. Menu names may differ.

Use the existing authorized session and select the individual company entity. The account owner handles authentication challenges.
Verify the rendered company when entity selection opens another tab.
Retain a full General Ledger and Trial Balance for the same period, including zero-ending accounts, with native entity, basis and date filters. Exact top-level menus must be verified in the current account.
A native CSV action can produce a second Download the file link. Follow it and retain the completed native file.
Preserve posted date, journal, transaction, document reference, account code and every split line.
Use GL posting dates for ledger controls; collect aging, receipts and check registers separately. Ordinary GL collection does not prove that corrections posted.

Evidence acceptance checklist

Retain entity, reporting basis, date and dimension filters.
Distinguish batch identifiers from documents and individual journal lines.
Check applied payments and credits separately from a GL export.

Fictional collection example

A fictional journal batch contains multiple invoice-related lines. One batch ID does not identify one invoice. Return document and line references with the entity scope. A consolidated balance that ties still needs a separate explanation before it is treated as the selected entity balance.

Invented teaching scenario, not a customer result or a reproduced vendor defect.

Capture the setup with the evidence

Company, legal entity or account, report name, period, basis, currency and timezone.
Selected filters, status, page count, original record identifiers and control totals.
Collection time, source route and authorized role. Record browser and automation versions when using a browser.
Original files and exceptions. Keep credentials, customer identifiers and financial artifacts private.

A browser version helps reproduce an interface issue. It does not validate the financial conclusion.

Pitfalls and stop conditions

Batch number is not one economic document. Consolidated reports can differ from an entity report. GL access alone does not certify posting.

How a plausible answer can go wrong

A balanced GL and trial balance can still omit cash, aging or other source families needed for close. A proposed correction file also does not prove which documents successfully posted.

Stop if account identity, permission, cutoff or population is uncertain. Return the missing evidence for review. Do not fill the gap with an invented record, a balancing entry or an assumed zero.

Read-only AI collection prompt

Replace the bracketed scope before use. This prompt collects evidence; it does not permit edits, approvals or accounting execution. Requesting an emailed report is a separate account action and requires explicit authorization.

Collect read-only evidence for Sage Intacct to answer [financial question]. Confirm [company], [account/entity], [period], [basis], [currency] and [allowed reports]. Use native GL/TB/report export filters and actual download links; retain entity, date, basis, report population and document identifiers. Verify applications and native read-back separately from GL collection. Retain original files, complete record IDs, counts, filters, collection timestamp and exceptions. Batch number is not one economic document. Consolidated reports can differ from an entity report. GL access alone does not certify posting. Stop if the source or scope is uncertain. Do not post, match, reconnect, delete or change settings. Return the evidence for financial review; do not claim the books are correct. Do not approve, submit payroll, pay, transfer, refund, send messages, invite users or accept terms. Stop at any login, MFA or credential prompt and hand back to the account owner. Store files only in [approved private location]. Do not paste customer artifacts into public tools. Use only preauthorized collection actions. Request an emailed report only when its delivery is explicitly authorized; otherwise ask the account owner to supply the file.

Next decision

What does the evidence support?

For each unresolved close item, identify the native document, every required line and the source family supporting it. Separate extracted, staged, posted and independently reviewed states in the owner handoff.

Compare the same population, identities and cutoff. Keep unsupported costs or settlements visible before using the result for pricing, cash or close.

Open the financial acceptance guide →

Sources and scope

Base product-reference scopes were reviewed 2026-10-06. The collection procedure retains its own review date in the dated sequence above. Individual source rechecks are dated with their citations. Operator decision guidance was reviewed 2026-10-07. The references below support their stated product scope, not every observed interface detail. It is not a vendor capability certification, a measured customer result or an independently reconciled account. Verify current features and entitlement in the account you use.

Sage Intacct official documentation
Journal batches, entries and queries, not native report reconciliation.

Content revision history