TieOut

Month-end reconciliation for Infor LX and Dynamics 365 Business Central

Your subledgers and your ledger disagree. TieOut tells you why.

TieOut reads your subledgers and your ledger, compares them, and traces every dollar of the difference to a cause: the document, the journal, and what went wrong between them. Infor LX with CEA, and Microsoft Dynamics 365 Business Central.

Read-only. It never writes to your ERP.On your premises. Your data stays with you.Fixed price assessment.
ACCOUNTS RECEIVABLE · COMPANY 1 · SEP 30
Subledger, open items (RAR)1,250,000.00
Ledger, control account 1200 (CEA)1,262,450.00
Manual journal to the control accountJ0002435, keyed by hand, no subledger document15,000.00
Posted in a different period2 invoices dated Sep 30, journals in October(8,200.00)
Batch not postedCash receipts applied, journal J0001647 unposted4,350.00
No journal producedCredit memo IN501419, event has no model1,300.00
UNEXPLAINED0.00
Difference of 12,450.00 explained. Nothing left over.

Why the net number misleads

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.

Net difference

12,450.00

What the month-end tie-out shows: ledger minus subledger.

Gross value of items

28,850.00

What is actually wrong: five items, four different causes, added without netting.

Unexplained

0.00

Every item is tied to a document and a journal. What cannot be attributed is shown as unexplained, never spread across other causes.

Figures from the TieOut sample company. The company and its data are invented.

What it finds

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 defaults

Batch not posted

The subledger is updated. The journal exists and was never posted.

journal status 2

Journal in error

The journal sits in error, so the ledger never received it.

journal status 1

No journal produced

A subledger transaction produced no journal at all.

missing event or model

Wrong account

The journal posted, to an account that is not the control account.

model account determination

Manual journal

Someone moved the control account by hand, with no subledger document behind it.

direct posting to control

Valuation difference

Ledger and subledger value the same transaction differently.

variance posted to control

Data problem

The subledger contradicts itself, such as a receipt still accrued on a closed PO line.

HPO against ITH

How it works

Four 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.

What you get

A findings report your controller and your auditor can both use.

  • A summary of every reconciliation: ties, explained, or unexplained remainder.
  • A bridge from the subledger balance to the ledger balance, cause by cause.
  • Every reconciling item with its source document and journal number.
  • What each cause means and where to look in the application.
  • An Excel workbook whose totals are formulas over the items, so it proves its own arithmetic.

Get the sample report

Excerpt from the sample report

ReconciliationDifferenceItemsGrossStatus
1 Receivables12,450.00528,850.00Explained
1 Payables(3,550.00)313,550.00Explained
1 Received not invoiced14,975.00624,775.00Explained
2 Receivables0.0000.00Ties
2 Payables0.0000.00Ties
2 Received not invoiced0.0000.00Ties

Sample company, invented data. Difference is ledger minus subledger.

Coverage

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.

Available

Roll-forwards and sign-off

Period-to-period movement, preparer and reviewer sign-off, audit evidence.

Available

Bank, card, marketplace and processor clearing

Bank and corporate card statements; undeposited funds; marketplace settlements (Amazon, Walmart, eBay); processor and buy-now-pay-later payouts (Stripe, Square, Affirm).

Available

Inventory to ledger

On hand at the ledger cost set against the inventory accounts: raw, sub-assemblies, finished goods, WIP, in transit, inter-company.

Available

Variance accounts

Purchase price and invoice price variances explained invoice by invoice: the period's activity against what the receipts and invoices should have produced. Usage, absorption and production next.

Available

Platforms

Infor LX and Business Central today. The method is not tied to either.

Every reconciliation runs on a canonical model that the LX adapter fills. A new platform is a new adapter, not a new product: the Business Central adapter is available now. Tell us which system you run and we will write when yours is ready.

Infor LX 8.x with CEA

BPCS 6.x and later on the IBM i. Available now; EGLi ledger next.

Available

Microsoft Dynamics 365 Business Central

Cloud or on-premises. Read through a signed read-only extension or published web services; same engine, same report. Available now.

Available

Infor XA (MAPICS)

Same IBM i, same read-only approach, different files.

PlannedTell me when it's ready →

Oracle NetSuite

Subledger detail against the general ledger through saved searches and SuiteQL.

PlannedTell me when it's ready →

QuickBooks

Desktop, Enterprise and Online: open items, bank feeds and processor payouts for companies that have outgrown the register. Pricing for QuickBooks companies on request.

PlannedTell me when it's ready →

What's next

Enhancements in the order we plan to build them.

Ask for the one you need and it moves up the list.

  1. Usage, absorption and production variances from the shop orders and the cost roll, joining purchase and invoice price variance.
  2. EGLi ledger beside CEA for LX sites on the newer general ledger.
  3. Preparer and reviewer separation: the approver cannot be the person who ran the reconciliation.
  4. Company-scoped users: each user sees only the companies assigned to them.
  5. Single sign-on against your directory (SAML or OpenID Connect).
  6. BAI2 and OFX bank statement formats alongside CSV.
  7. Infor XA, then NetSuite and QuickBooks adapters.

Security

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.

  • 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.
  • Tested on IBM i V7R5 over the open-source JTOpen driver, with exact decimal handling end to end.

Pricing

Start with a fixed-price assessment.

Invoiced and paid by ACH or wire, the way you pay any other vendor. No card required.

Assessment

$12,500 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

$30,000 per year

TieOut installed at your site, run by your team every month-end.

  • 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.

About

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. He has been a CEA financial consultant since BPCS 6.0 and served as the primary financial help-desk consultant for SSA Global Technologies.

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.

Founding customer

One company. The assessment fee credited in full.

TieOut is taking one founding customer for an assessment starting in January 2027. The assessment is the standard engagement: one month-end, every control account reconciled and every difference explained, using the generally available release in read-only mode on your own server, for the standard fee of $12,500.

What is different: if you subscribe within sixty days of the findings report, the whole assessment fee is credited against your first-year subscription. If you do not subscribe, the fee stands and you keep every deliverable. In return we ask for a written reference and one case study, each approved by you in writing before any use.

Applications close January 9, 2027. One company is selected by Priceless Plus Corporation; this is not a drawing. Eligible systems: Infor LX 8.3 or 8.4 under Infor maintenance, or Dynamics 365 Business Central.

Apply to be the founding customer

What you receive

  • The findings report: every reconciling item by cause, with the document and the journal.
  • The item workbook, with totals that are formulas over the items.
  • The statement log: every query sent to your system.
  • A two-hour walkthrough with your finance team.
  • Fifteen business days from server and profile to report.

Terms are in the Assessment Statement of Work, Schedule 2 (Founding Customer Terms), provided on request.

Sample report

See what we would find in your month-end.

Tell us where to send the sample findings report and workbook, or ask for a note when TieOut supports your system. If you would like to talk about an assessment, say so in the note.

Or write to support@erptieout.com.

I would like