TRANXACT.AI Help

Documents, headers and line items

How a transactional document is put together, why its totals always agree with its lines, and when the lines stop changing.

Every transactional document opens onto a detail page: a header summary above, line-item grids below, reached from the Detail action on its list. The header can be edited in place from that page — which is where you are standing when you have just read the document and seen what is wrong with it.

Lines are a grid, not a blob

Lines are entered in a grid: pick the item or the GL account from a dropdown, type the quantity, watch the running total. Documents whose header and lines are written together — journals, requisitions, purchase orders, supplier invoices, opportunities — carry that same grid inside the creation form, so the document is made in one act rather than created empty and filled afterwards.

ModuleDocumentWhat the lines are
AccountingJournalsPosted lines: account, debit, credit. Immutable.
AccountingAP and AR invoicesCosted lines with item, GL account and tax.
CRMOpportunitiesProduct lines, which become the AR invoice on Closed Won.
CRMField work ordersTasks with labour and technician, plus parts drawn from inventory.
Supply ChainRequisitions and purchase ordersItem lines showing received and outstanding quantities.
Supply ChainReceiptsReceived quantities by bin and lot. Immutable.
HRMSPayroll runsA payslip per employee: gross, tax, deductions, net.
ManufacturingProduction ordersBOM-exploded components and routing operations.
ManufacturingQuality inspectionsMeasured characteristics against their spec limits.
EHREncountersBillable charge lines.
Student LifecycleTerm billingCharges from registration, netted against accepted aid.

Two rules enforced in the API, not merely in the screen

The grid tells you which of the two it is rather than letting you type and then failing on save. "Posted" and "the period is closed" are different problems with different answers, and being told the wrong one costs an afternoon.