Two-person control into the accounting system, and a revert that never deletes history.
Status at ebf7cf0: Gap — posting metadata columns and read-only finance feeds exist.
The request and approval gates, the 27-column posting action, the direct writer, the reasoned revert and the compensating entry are not implemented.
Account has verified the itemize and requests posting to AutoCount.
Four companies, four AutoCount files. Each file has twelve in-house service sheets and one Sub Con sheet.
| Reads | Picks |
|---|---|
the line's work_done_by |
which sheet — in-house service sheet, or the Sub Con sheet |
| the item's Sales ACC No. | which account |
The Item Master maintains the Sales ACC No. mapping. Sales, OE and field workers do not choose or see it during normal work. When Account generates the AutoCount template, the system reads each itemize row's Item Master ID, looks up the Sales ACC No. and writes it into the template. The exported payload keeps the exact value used, for audit after posting.
Posting freezes the exported invoice or payment facts: entity, Debtor Code, Bill-To snapshot, lines, prices, discount, total, document date and AutoCount reference.
Posting does not lock the whole customer profile or stop later operational job logs.
An authorised person may use Controlled Correction with a compulsory reason.
Keep the previous posted payload so the system can show what AutoCount currently contains.
Audit history alone is not enough to replace the posted snapshot.
The e-Invoice is AutoCount's, submitted from AutoCount's own MyInvois link — mandatory since January 2026. It is not a Sales Module document.
Story. As Account, I want to submit a posting request from the Verified snapshot, so that accounting receives reviewed data.
Acceptance. The request records the frozen company, Verified snapshot, requester and time.
Story. As a Finance Manager, I want to approve or reject another person's request, so that posting follows two-person control.
Acceptance. The approver cannot be the requester; rejection requires a reason.
Story. As a Finance Manager, I want a reasoned revert through a compensating entry, so that posted history is never silently deleted.
Acceptance. Revert records original document, reason, actor, time and compensating reference.
Story. As the system, I want approved AutoCount output to use the frozen company and Verified snapshot, so that invoices reflect approved truth.
Acceptance. The output records document reference, posting actor and timestamp and is idempotent.
Posting metadata columns and read-only finance feeds exist. Today a read-only feed of verified rows is served to the Account team's AR Portal, which owns the posting.
A browser CSV export is still live on two screens.
Invoice generation still reads finalized rather than verified, and the company freezes at dispatch.
| # | Question | Who decides |
|---|---|---|
| Q1 | How the overall discount posts — proportionately across lines, or one separate discount line with its own account | Accounts |
| Q2 | Document date for a multi-visit job — first visit, last visit, or one posting per visit | Accounts |
| Q3 | Who owns the two gates and the revert | Charlie / Accounts |
| Q11 | Which account an OTHER line posts to — proposed 599-9990 | Accounts |
New to these terms? See the Glossary.