App catalogue Finance

Manual journal entry approval

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.

SCREENSDATA HANDLERSSOURCE OBJECTS, READ IN PLACES01 New entryscreenS02 ChecksscreenS03 ReviewscreenS04 ApprovalscreenS05 Posting resultscreendh_glJournal linedh_cost_centerCost centerdh_budgetBudget linedh_employeeEmployeeS/4HANAACDOCAS/4HANACSKS · CSKTS/4HANABPGE · BPJAS/4HANAPA0001 · PA0002rows stay in the source · access rules apply at read time · writes go through the source's released interface and are confirmed
The screens, the data handlers behind them and the objects each handler reads in place on S/4HANA. Other systems have their own page.
4 days
of configuration to a production-grade version
estimate
6
screens, desktop and mobile
catalogue
4
data handlers, read in place
catalogue
4
systems with a page for this app
catalogue
3
clocks with escalation
catalogue
What it does

Today, and with the app

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.

Who takes part

Process app: lanes and boxes first, then screens per box, then roles, then the criteria on each arrow

LaneDoes
Preparerbuilds the entry with lines and support documents
Reviewerchecks accounts, support and period; passes or returns
Approveraccounting manager up to 250,000; controller above
Auditorreads the log of entries, support and approvals on a self-service screen
Screens

6 screens, composed from the handlers

Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.

ScreenWhat is on it
S01 New entryheader: company, period, posting date, reason; lines: account, cost center, debit, credit, text; running balance; support upload; submit
S02 Checksaccount 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 Reviewlines with the support documents beside them, flags, comment; pass or return
S04 Approvalsummary by band, flags, budget effect; approve or reject with a note
S05 Posting resultdocument number from the ledger, posting date, link to the support; schedule reversal in the next period
S06 Logentries by preparer, reviewer, approver, status, value and period; auditor filter and export
Data handlers

4 objects, read where they live

The first object is the main one; each system page shows the real table or resource behind every handler.

ObjectWhy the app reads itSee it on
Journal linejournal lines: account, amount, cost center, posting date, period, userS/4HANA · Oracle Fusion · Workday · Snowflake
Cost centerowner and validity of each cost center on the entryS/4HANA · Oracle Fusion · Workday · Snowflake
Budget lineplan amount for the account and cost center, to show the effectS/4HANA · Oracle Fusion · Workday · Snowflake
Employeepreparer, reviewer and approver with their org unit and manager, for the separation of dutiesS/4HANA · Oracle Fusion · Workday · Snowflake

Written back

ObjectWhat changes
Journal linejournal document posted through the ledger interface with lines, text and the support reference; reversal posted in the next period when scheduled
The flow

From the trigger to the last write

THE FLOW · MANUAL JOURNAL ENTRY APPROVAL1Entry submitteddebits equal credits;support attached; periodopen2Checks passedaccounts and cost centersvalid on the posting date;duplicate check clear, orthe preparer explains thematch3Reviewedreviewer differs from thepreparer; passes or returnswith a comment4Approvedup to 250,000: accountingmanager; above 250,000:controller5Posteddocument number returnedfrom the ledger withinseconds; entry locked; logupdated; reversal scheduledwhen asked
Each step and the criterion that moves it.

Start: A preparer submits S01 with lines that balance to 0 and at least 1 support document.

StepMoves when
Entry submitteddebits equal credits; support attached; period open
Checks passedaccounts and cost centers valid on the posting date; duplicate check clear, or the preparer explains the match
Reviewedreviewer differs from the preparer; passes or returns with a comment
Approvedup to 250,000: accounting manager; above 250,000: controller
Posteddocument number returned from the ledger within seconds; entry locked; log updated; reversal scheduled when asked
Actions, clocks and measures

What the components do, what the clocks enforce, what the board shows

ComponentTrigger → action → outcome
grd_lineson 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_submiton 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_approveon click → record the approval → call the ledger posting interface with the lines and the support reference, store the document number
btn_reverseon click → post the reversal in the next period through the reversal interface → link both documents in the log

Clocks

StepTime limit and escalation
Review1 working day, then the accounting manager is reminded
Approval1 working day, or 4 working hours in the last 3 days of close, then the controller is copied
Closeentries submitted on the last day of close are flagged to the close lead

Measures

entries posted within 1 day of submissionentries returned by reviewersmanual entries per period by companyvalue approved by bandentries submitted on the last day of close
A day with the app

Illustrative

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.

illustrative scenario · Manual journal entry approval
On your systems

One page per system

The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.

Other systems connect through the same handlers; see how SmartApps connect.

Terms on this page

Manual journal entryA posting to the ledger that a person creates, with accounts, amounts, text and support documents.
AccrualAn entry that records a cost in the period it belongs to, before the invoice arrives, and reverses in the next period.
Separation of dutiesThe rule that the person who prepares an entry differs from the person who reviews or approves it.
Questions

How long does it take to have this running?

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.

Which system does it run on?

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.

Who takes part from outside the company?

Every role in this app is inside the company; an outside role can be added as a lane with a portal screen.

What does the audit record hold?

Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.

See this app on your data

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.