Specforge

Special functions · Post Any FI Document

Any FI document — post, reverse, reclass, revalue. Bulk or single, any channel.

Post any FI document — one or thousands, from any boundary system — then operate on what's posted: reverse it, reclass it to the right account or cost object, or revalue inventory (MR21/MR22). Inbound interfaces become registered channels that normalize any format into canonical FI staging documents, validated all-or-nothing at the gate; reversals, reclasses, and revaluations post through the same pipeline. The error-resolution workflow includes the people SAP's tooling can't: the external owners of the boundary systems.

Open the Post Any FI Document demo →

01 · The landscape

What the market has

SAP AIF
Native interface monitoring + error handling in S/4
The gap: Volume-based costs, and every participant needs an S/4 license — boundary-system owners can never join. Have AIF? We complement it: internal resolution stays there, mirrored into the gateway. Don't have AIF? The gateway IS your AIF-equivalent, at flat cost
SAP Integration Suite (CPI)
SAP's middleware
The gap: Pipes, not FI semantics — and priced per message volume
MuleSoft / Boomi
Generic iPaaS
The gap: Every interface is still a project; connection-based pricing
TIS / Serrala
Payment and bank-format hubs
The gap: Payments only — one document family of five

02 · Differentiators

Where we differ

  • The channel registry is the product: registering boundary system #20 is configuration, not an interface project
  • All-or-nothing gatekeeping — malformed transmissions bounce with row-level findings; S/4 never sees a bad interface again
  • Error resolution in two modes: with AIF, internal steps stay there (mirrored into the gateway) while externals work in the gateway; without AIF licenses, the gateway's workcases are your full AIF-equivalent — same chains, internal and external, any depth
  • Flat per-month cost with unlimited documents, against message-metered and document-metered alternatives

03 · Functionality

What we built

  • Channel registry with owner, target document type, and mapping profile per boundary system
  • Normalization to canonical FI staging documents: journals, AP/AR invoices, incoming payments, bank statements — proper posting keys throughout
  • Typed gate validations (journals must balance; payout files must satisfy net + fees = gross; statements pair bank vs clearing)
  • Duplicate-transmission protection per channel; full message ledger with staging-document journals
  • Error workcases auto-opened on rejection, with configurable external + internal resolution chains
  • Reverse posted documents (FB08 / mass F.80) — flipped Dr/Cr with reversal reason + date, original and reversal cross-linked
  • Reclass to the correct GL account or cost object (cost center / profit center / WBS), single or bulk
  • Revalue inventory (MR21 price change / MR22 value adjustment) across valuation areas, views, and currencies — posting exactly the combinations loaded

See it working — today

The demo runs the complete loop on live data: capture, decide, govern, post, audit. No process change required on day one.

Open the Post Any FI Document demo

All special functions