ServicesPayroll

The payroll journal entry, built for you. Posted only on your click.

After each payroll run, an agent builds the journal entry from the reports your payroll provider sends, with the month-end accrual and its reversal when a pay period crosses the month. It checks every line, and the controller reviews it and posts it. lumic builds it on site and keeps it working.

How it works

From the payroll reports to a posted entry. The controller signs off.

  1. It reads the reports.

    The controller drops the reports the payroll provider sends after each run into one place. The agent recognises each file by what it contains, not by its name.

  2. It builds the entry.

    It builds the payroll journal entry with posting rules drawn from your own posted history, and the accrual and reversal when a pay period crosses the month.

  3. The controller posts it.

    The controller reviews the entry and posts it with one click. Nothing is written to the books before that click.

The checks

Every line checked before anyone posts.

The agent proves the entry before the controller sees it, and it runs every check again at the moment of posting.

01

Balanced to the penny

Every entry has to balance, or it can’t be saved. The entry total must tie to the payroll provider’s total, and per-person lines are proved against the payroll register where there is one.

  • Debits equal credits
  • Ties to the provider’s total
02

New lines stop the run

A line the agent has never seen is not guessed. The controller picks the account from a shortlist, and the agent remembers that choice for every later payroll.

  • No guessing
  • Learns each decision once
03

A short review screen

The controller sees the totals reconcile, debits equal credits, and which lines need a decision, each with its evidence. The agent then runs a full check against the accounting system without posting anything.

  • Evidence for every decision
  • A dry run before the post
04

Guards inside the write

When the controller clicks post, every guard runs again: balanced, active accounts only, a duplicate check, and a check that it writes to the right company. It stops at the first failure.

  • Only on the controller’s click
  • Stops at the first failure
05

Never posted twice

Each posted entry is logged with its transaction number, and the source files are fingerprinted. A posted payroll can’t be rebuilt or posted twice.

  • Every post logged
  • Duplicate-proof
06

Month-end ready

When a pay period reaches back into the previous month, the agent builds the accrual and its reversal, so the month closes on the right numbers.

Other jobs lumic automates: Services. Examples in production: Portfolio. The method: How lumic works.

Based in St. Louis. Start with a conversation.

Christian GonzenbachJoshua Wittenauer

Every engagement is led by a senior FDE, on site.

How to start
  1. 1
    A 20‑minute call.You walk the team through the work your people do by hand.
  2. 2
    A written proposal.What lumic would build, the timeline, and the cost.
  3. 3
    An on-site visit.lumic’s FDEs meet your team where the work happens and confirm the plan. St. Louis first; they travel for the right fit.