Your subledgers and
your ledger disagree.
TieOut tells you why.
TieOut reads your Infor LX subledgers and your CEA ledger, compares them, and traces every dollar of the difference to a cause: the document, the journal, and what went wrong between them.
Read-Only
It never writes to LX.
On Your Premises
Your data stays with you.
Fixed Price
Assessment, no surprises.
A control account that is off by 12,450
can be carrying 28,850 of problems.
Reconciling items of opposite sign cancel each other. A small difference at month-end is not evidence of a clean subledger; it is often several unrelated faults that happen to offset. TieOut reports both figures, so you see what the net is hiding.
What the month-end tie-out shows: ledger minus subledger.
What is actually wrong: five items, four causes, added without netting.
Every item is tied to a document and a journal. Nothing is spread across other causes.
Eight causes. Each one points
to a place in LX.
Because LX is built from subsystems that post to CEA through events and models, differences have a small number of mechanical causes. TieOut sorts every item into one of them.
Posted in a Different Period
The document is dated in the period; its journal landed in another.
cutoff, posting date defaultsBatch Not Posted
The subledger is updated. The journal exists and was never posted.
journal status 2Journal in Error
The journal sits in error, so the ledger never received it.
journal status 1No Journal Produced
A subledger transaction produced no journal at all.
missing event or modelWrong Account
The journal posted, to an account that is not the control account.
model account determinationManual Journal
Someone moved the control account by hand, with no subledger document behind it.
direct posting to controlValuation Difference
Ledger and subledger value the same transaction differently.
variance posted to controlData Problem
The subledger contradicts itself, such as a receipt still accrued on a closed PO line.
HPO against ITHFour steps, and your system
is never written to.
Connect
You create a read-only profile on the IBM i. TieOut connects with the open-source JTOpen driver. No IBM or Infor software is installed.
Extract
TieOut reads the files it needs with plain SELECT statements and explicit column lists. Every statement is logged and yours to review.
Reconcile
Each subledger transaction is linked to its journal through the CEA cross-reference. Subledger and control account are compared in the designated book.
Report
You receive a findings report and a workbook holding every item. The workbook recomputes every total from the items.
Built in release order,
starting where month-end hurts most.
TieOut targets Infor LX 8.x with the CEA ledger first. The same method extends to the clearing accounts that no subsystem report covers.
Receivables, Payables, Received Not Invoiced
RAR, APH and AMH, HPO with ITH, against CEA.
Bank, Marketplace and Card Clearing
Amazon and merchant settlements, cash accounts.
Inventory to Ledger
On-hand at the ledger cost set against the inventory accounts.
Corporate Cards, Roll-Forwards, Sign-Off
Period-to-period movement and audit evidence.
Designed for the question
your IT manager will ask first.
TieOut is installed beside your IBM i, inside your network. It is not a hosted service and we do not hold your financial data. Tested on IBM i V7R5 over the open-source JTOpen driver, with exact decimal handling end to end.
Read-Only by Construction
The adapter can only issue SELECT statements. Use a profile with read authority to the LX files and nothing else.
A Complete Statement Log
Every query sent to your system is recorded and handed to you with the report.
No Change to LX
No objects installed on the IBM i, no triggers, no modifications to Infor code.
Your Data Stays Put
The working database runs on a server you control. Nothing is sent to us.
Start with a fixed-price assessment.
Assessment
Fixed · One month-end, reconciled and explained
- Receivables, payables and received not invoiced, every company
- Findings report and item-level workbook
- The statement log of everything read
- A walkthrough of the findings with your team
50% at signing, 50% on delivery of the report.
Subscription
Installed at your site, run by your team
- Browser-based, no green-screen work
- New releases as coverage extends
- Application support by email
- Installed with you, on a server you control
Early access. Support covers the application; the accounting decisions remain yours.
Built by someone who has closed
the books on BPCS since version 3.
TieOut is the work of Gee Corder, an independent ERP consultant with more than 30 years in the field and over 25 as a principal BPCS and Infor LX consultant. The product exists because the same month-end conversation kept happening: the subledger and the ledger disagree, nobody knows why, and finding out takes days of queries. The causes are mechanical and few. Software should find them.
Or visit erptieout.com · Write to support@erptieout.com