Takes a manual journal entry with its support documents through checks, review and approval by amount band, and posts it to the ledger on approval.
Today a manual entry is a spreadsheet template emailed to a reviewer, approved in a reply, and typed into the ledger by the preparer. The support documents sit in a shared folder, and the auditor asks for them months later.
The preparer builds the entry on one screen: header, lines with account, cost center, debit and credit, text, and the support documents beside them; the balance is checked as lines are typed. On submit the app checks the accounts and cost centers on the posting date, the open period, and duplicates against the entries of the last 30 days, and shows the effect on the budget of each cost center. A reviewer from the same company, apart from the preparer, passes or returns the entry, and the approver of the amount band approves it. The app then posts the document through the ledger interface, stores the document number beside the support, and can schedule the reversal in the next period from the same screen.
| Lane | Does |
|---|---|
| Preparer | builds the entry with lines and support documents |
| Reviewer | checks accounts, support and period; passes or returns |
| Approver | accounting manager up to 250,000; controller above |
| Auditor | reads the log of entries, support and approvals on a self-service screen |
Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.
| Screen | What is on it |
|---|---|
| S01 New entry | header: company, period, posting date, reason; lines: account, cost center, debit, credit, text; running balance; support upload; submit |
| S02 Checks | account and cost center validity on the posting date, period open, balance at 0, duplicate check against the last 30 days, budget effect per cost center; pass or flags |
| S03 Review | lines with the support documents beside them, flags, comment; pass or return |
| S04 Approval | summary by band, flags, budget effect; approve or reject with a note |
| S05 Posting result | document number from the ledger, posting date, link to the support; schedule reversal in the next period |
| S06 Log | entries by preparer, reviewer, approver, status, value and period; auditor filter and export |
The first object is the main one; each system page shows the real table or resource behind every handler.
| Object | Why the app reads it | See it on |
|---|---|---|
| Journal line | journal lines: account, amount, cost center, posting date, period, user | S/4HANA · Oracle Fusion · Workday · Snowflake |
| Cost center | owner and validity of each cost center on the entry | S/4HANA · Oracle Fusion · Workday · Snowflake |
| Budget line | plan amount for the account and cost center, to show the effect | S/4HANA · Oracle Fusion · Workday · Snowflake |
| Employee | preparer, reviewer and approver with their org unit and manager, for the separation of duties | S/4HANA · Oracle Fusion · Workday · Snowflake |
| Object | What changes |
|---|---|
| Journal line | journal document posted through the ledger interface with lines, text and the support reference; reversal posted in the next period when scheduled |
Start: A preparer submits S01 with lines that balance to 0 and at least 1 support document.
| Step | Moves when |
|---|---|
| Entry submitted | debits equal credits; support attached; period open |
| Checks passed | accounts and cost centers valid on the posting date; duplicate check clear, or the preparer explains the match |
| Reviewed | reviewer differs from the preparer; passes or returns with a comment |
| Approved | up to 250,000: accounting manager; above 250,000: controller |
| Posted | document number returned from the ledger within seconds; entry locked; log updated; reversal scheduled when asked |
| Component | Trigger → action → outcome |
|---|---|
| grd_lines | on edit → validate the account and the cost center on the posting date and sum debits and credits → show the balance and enable submit at 0 |
| btn_submit | on click → run the duplicate and period checks → route to a reviewer of the same company, apart from the preparer, and start the 1-day clock |
| btn_approve | on click → record the approval → call the ledger posting interface with the lines and the support reference, store the document number |
| btn_reverse | on click → post the reversal in the next period through the reversal interface → link both documents in the log |
| Step | Time limit and escalation |
|---|---|
| Review | 1 working day, then the accounting manager is reminded |
| Approval | 1 working day, or 4 working hours in the last 3 days of close, then the controller is copied |
| Close | entries submitted on the last day of close are flagged to the close lead |
Names, places and figures are illustrative; the pattern is the catalogue's.
On the second day of close, at 16:45, Carlos, an accountant in São Paulo, submitted an accrual of 180,000 for freight invoices due in the next period, with the carrier statements attached. The checks passed within seconds, his reviewer passed the entry at 17:20, and the accounting manager approved at 08:30 the next morning. The document number appeared in SAP a minute later, and the reversal for the next period was scheduled from the same screen. The log showed the auditor every manual entry of the quarter with its support and approvals.
The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.
Journal line read from ACDOCA (universal journal); also on SAP ECC.
Open the S/4HANA page →Journal line read from General Ledger REST: journals · BICC GL journal lines extract; also on Oracle E-Business Suite.
Open the Oracle Fusion page →Journal line read from Financial_Management: Get_Journals; HCM / finance.
Open the Workday page →Journal line read from CONFORMED.JOURNAL_LINE · HISTORY.JOURNAL_LINES; lakehouse.
Open the Snowflake page →Other systems connect through the same handlers; see how SmartApps connect.
About 30 minutes to a first running screen on your live rows, and 4 working days to the production-grade version described here, most of it spent agreeing screens and criteria with the process owner.
Any of SAP S/4HANA, Oracle Fusion Cloud, Workday, Snowflake, with the objects read in place; the pages above show the objects and the write path for each. Two systems at once is one handler per object per system.
Every role in this app is inside the company; an outside role can be added as a lane with a portal screen.
Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.
Bring the process and the systems it touches. In the first session we register the data handlers, draw the levels or the lanes and run the first screen on your live rows.