Order records, processor activity and bank deposits, organized into a source-linked reconciliation for your bookkeeper to review. Fixed scope, $2,500, ten business days. Start with a synthetic example by email.
Email-first, no sales call required. Secure export intake is agreed before client files are shared. Free check: one processor, one payout period, within two business days after usable inputs and agreed handling.
The difference stays open until supporting evidence resolves it.
My name is Adrian Penn. I work in accounts receivable and cash operations at a Fortune 500 company, checking that records across different systems actually match before anything gets reported. Before that, two years in customer success operations at a startup, ending up in the management operations role, working closely with ecommerce finance, payment disputes, and the operational side of what happens when a transaction doesn't go as planned. I started Luminary Solutions because I kept seeing the same problem: sellers running Shopify alongside Stripe, PayPal, Amazon, sometimes all three, with nobody actually checking that the money matches the orders until tax time forces the question.
It's sales, minus fees, minus refunds, minus chargebacks, bundled into a single number that lands on a different day than the sales that made it up.
Orders and settlement records linked where the supplied evidence supports a match. Fees and reversals are identified, and unmatched items stay visible alongside the formulas.
Anything that didn't match cleanly, flagged with exactly what's needed to resolve it. Nothing gets silently estimated.
Order value, sales before tax, fees, refunds, dispute principal, expected settlement, payout gaps and open exceptions. Accounting revenue is reported only when the evidence supports it.
View a synthetic reconciliation example (PDF) before you send anything.
A difference can reflect timing or transaction detail rather than an error. These are examples of what the source records may explain.
Processor fees may be deducted before settlement. We use the processor's transaction detail to separate those fees from the amount deposited.
A refund issued in October against a September sale reduces an October deposit, not the September one. Pull any single month in isolation and the numbers will disagree with the orders that actually happened in it.
A bank deposit may combine many orders. The processor's payout and transaction identifiers provide the link to the underlying records; missing links remain exceptions.
Some processors hold back a percentage of each payout as a reserve, releasing it weeks later. That reserve release shows up as its own deposit, unconnected to any order on the day it lands.
A sale priced in one currency and paid out in another converts at whatever rate the processor used that day, not the rate your storefront displayed. That gap alone can make an otherwise correct order look wrong.
After agreement, receive a secure intake checklist and deposit invoice. Production starts when the deposit is available and the agreed exports are complete.
Each processor reconciled independently in its own clearing account, then flagged exceptions sent back for anything that needs a document I don't have.
Final payment, then the full package: reconciled dataset, exception log, dashboard, and a one-page summary for your accountant.
Luminary Solutions is new. Rather than fill this space with stock testimonials, here's what's true right now: every deliverable gets a full manual QA pass against an automated numeric consistency check before it ships, and every client is asked, with their explicit permission first, whether their experience can be shared here. This section will hold real feedback as soon as there is some, not before.
Reconciliation Sprint
Dates, processors, transaction volume and required exports agreed before signing.
When your firm needs subcontracted help with a defined reconciliation, review a synthetic example before sharing any client data.
Your firm keeps the client relationship and reviews the output. I return the source trail, calculations and unresolved items for the agreed scope. Sample review, scope questions and progress updates can be handled by email. Calls are optional and arranged by mutual agreement.
Yes. This service uses AI-assisted processing, source-based checks and review before delivery. The agreement identifies the processing services and data-handling arrangements before you share files. Any use of Anthropic Claude or OpenAI Codex must match those agreed arrangements. AI output does not replace accounting or tax judgment.
No. I reconcile and organize the supplied data. Your accountant or legal adviser handles questions requiring accounting, tax or legal judgment.
We first assess the available exports and agree the scope. Missing records and unexplained differences are listed with the evidence needed to investigate them.
Bookkeeping can include reconciliation. Luminary provides a defined export-to-evidence project: source-linked calculations and open exceptions for your bookkeeper or accountant to review and use.
First, the period, processors, approximate volume and available export types. We confirm scope and secure handling before requesting files. A checklist and deposit invoice follow the agreement.
No obligation, no login access, no sales call required to get started.