Light in Mexico
Built for how Mexico does business
Run your Mexican entities on the same platform as the rest of the world. NIF reporting, IVA and withholding applied at posting, CFDI 4.0 stamped through a certified PAC, and the full SAT filing cycle — handled by agents, reviewed by your team.
Book a demo
The world's most demanding finance teams run on Light.
Everything a finance team in Mexico needs
Whether you're expanding abroad from Mexico or landing there as a global company, Light keeps every entity on one ledger.
01
NIF
Report under Mexican Financial Reporting Standards (NIF) and group standards side by side with multibook — no parallel spreadsheets.
02
IVA
Standard 16%, the reduced border-region rate, zero-rated and exempt supplies applied via tax codes as transactions post — with IVA and ISR withholding handled as their own tax types.
03
CFDI 4.0
Issue and receive CFDI 4.0 stamped through a certified PAC — invoices, credit notes, payment complements, and withholding certificates, outbound and inbound.
04
Mexican banking
Connect Mexican bank accounts via host-to-host integration or bank feeds — transactions reconcile automatically, vendors get paid by SPEI to their CLABE in MXN.
IVA, from CFDI to the SAT
In Mexico the invoice is the tax filing. Light stamps every document at source and builds the monthly returns from the same postings — nothing reconciled after the fact.
-
CFDI 4.0, both directions
Every sales invoice is stamped as valid CFDI 4.0 XML through a certified PAC — RFC, régimen fiscal, uso del CFDI, and código postal validated before it goes out — and supplier CFDIs arrive through the same connection, matched to bills in your AP workflow with no re-keying. Cancellations follow the SAT's acceptance rules, with each document's UUID and status tracked on the ledger entry itself.
-
Cash-basis IVA and the payment complement
Mexican IVA is recognized when cash moves, not when the invoice is issued. Light issues the complemento de pago on settlement and shifts the IVA accordingly, so acreditable and trasladado balances match what the SAT expects on the monthly declaration.
IVA and ISR withheld on payments to service providers post to their own accounts and flow into the withholding CFDIs and the DIOT automatically.
The periodic compliance cycle
Every recurring Mexican obligation is fed by the same CFDIs and postings — which is why one ledger matters.
01
IVA and ISR declarations
Monthly, by the 17th of the following month — filed from balances built continuously in the ledger
02
Contabilidad electrónica
Monthly XML upload to the SAT — chart of accounts, trial balance, and journal entries generated straight from the ledger
03
DIOT
Third-party transaction report, built from supplier CFDIs and payments already recorded
Compliant with how Mexico audits
Mexican statutory requirements are built into the ledger, not bolted on.
01
SAT-verified trail
Every invoice carries its UUID, stamp, and cancellation status, so the audit trail starts at the tax authority itself.
02
Contabilidad electrónica
The código agrupador mapping, trial balance, and pólizas the SAT requires are generated from the ledger, not assembled by hand each month.
03
Host-to-host banking
Direct connections with major Mexican banks for statement collection and SPEI payment files at treasury-grade control.
One platform, every country you operate in
Mexico is one of the many countries Light supports out of the box — same ledger, same close process, local requirements handled per entity.
What it replaces
Replace the ERP.
Lose the Frankenstack.
The ERP was built for a different era. The Frankenstack just patched its gaps. Light replaces both, and what you keep connects as an app.
The Frankenstack ERP · Accounts payable · Accounts receivable · Cards · Bank · CRM · Spreadsheets · Bank connectors · Tax software
Replaces ERP
- NetSuite
- Microsoft Dynamics
- Sage Intacct
- SAP
- One Xero or QuickBooks per entity
Replaces tools
- Card and expense tools such as Pleo, Spendesk and Ramp
- Bill pay products
- Subscription billing tools
- Consolidation spreadsheets
Connects as apps
- Your banks
- Payroll
- CRM
- BI and planning tools
- E-invoicing networks
Migration
Officeguru was live in 7 days.
Leave your frankenstack behind. Work with Light or an implementation partner using Light’s methodology and quality standards to build the Light you need.
1
Connect the source
2
Clean and map with agents
3
Review & go live
How it works
Agents do the work. Your team approves.
That is the pattern across Light: agents work inside the policy you write, and your team approves what needs a human. Take one example, a supplier bill.
1. The invoice arrives.
Forward a supplier PDF to your Light inbox. It becomes a draft bill in the same system as your ledger.
Explore bill payments2. An agent codes it.
The Bill Agent reads the invoice and codes the draft, using your instructions and that vendor’s previous bills.
Meet the agents3. Your team approves.
Approval follows the rules you set for entity, vendor or amount. Anything that needs attention is corrected before it posts.
See approval workflows4. It posts to the ledger.
Approval posts the bill to the ledger, ready for payment. Follow the entry through entity and group reports.
See reportingCustomers
What changed for the finance teams that moved.
The platform
Light ledger. Light apps. Light agents.
Start with one set of books for every company you own. Add only what your business needs, when it needs it. Then let the routine work happen on its own, within the rules your team sets.
Knows the business.
Every company you own, every country, every number, on one ledger. Accounting, payables, receivables, cards and consolidation share it, so you move from the group view to the transaction behind any number.
See the ledgerAdapts to the business.
In Light, a connection is an app. The App Store has 600+: your banks, payroll and CRM, plus apps for mileage, per diems and reporting. They heal and improve over time instead of aging.
Explore the appsOperates the business.
Agents code the bills, clear the bank, book the month-end accruals and chase the missing receipt, inside the policy your team writes: what runs on its own, what needs review, and who approves. Every action is logged to the agent that took it.
Meet the agents
Customer story
“Group entity management has saved every member of the team hours and hours.”
Harriet Stewart · Head of Business Systems, Tillo
Tillo replaced eight ledgers with one and reduced its close from 12 days to 5 across four entities.
Read the Tillo storyCompliance
Built for global businesses.
For finance teams managing multiple entities, currencies and countries. Explore the controls and e-invoicing coverage for your requirements.
Migration
A clear plan from migration to first close.
Agree your entities, data, integrations and timeline before you start. Light or an implementation partner leads delivery, with a named lead accountable for the project and Light’s methodology and quality standards.
Agree responsibilities and integration needs. Bring your chart of accounts, balances and open items into a guided dry run.
Configure workflows together, reconcile the imported balances and test real transactions. Your team signs off each process.
Your team approves the final setup before cutover. Support continues through your first month-end close, so you can run Light yourselves.
The questions CFOs ask first.
“How long does implementation take?”
Plan for 4–16 weeks from signature to your first month-end close. The timeline depends on your entities, data readiness and integrations; we agree the scope and milestones with you. Go-live is one milestone within that plan.
“What happens to our history?”
We agree the history to migrate as part of your scope. Opening balances and open items are in place for go-live; historical transactions can follow. All Gravy brought six years of history into Light, with each year reconciled before import.
“How do we know we are ready to switch?”
Your team reconciles the migrated balances and tests real transactions, workflows and integrations. Formal sign-off gates go-live. We agree the cutover and ledger close dates together, with support through your first close.
“Who manages implementation—and who runs Light afterwards?”
We agree the delivery team, scope and responsibilities with you before implementation begins. Your project is led by Light or an implementation partner working to Light’s methodology and quality standards, with a named lead accountable for delivery. Your finance team reviews and approves the setup before go-live. Afterwards, they run Light day to day, with the knowledge to manage workflows and make changes themselves.
Why we built Light
Finance should help shape the business.
Your team should spend less time moving numbers between systems and more time deciding what comes next.
That belief is why we built Light. Read the thinking behind it.
Jonathan Sanders · Co-founder & CEO
Read the manifesto