Invoice sync into Light's AR

Open invoices flow from Solvimon into Light with their state transitions (issued, partially paid, paid, credited). Bank-transfer invoices are chased and matched in Light; paid status syncs back to Solvimon

Journal entry sync into the ledger

Every billing transaction (subscriptions, usage, credits, mid-cycle amendments, credit notes, refunds) posts to Light's general ledger automatically, mapped to the right entity

Multi-entity roll-up

Commitments billed on a parent entity with usage consumed by child entities reconcile correctly, with intercompany entries eliminating as they post

Agent-run close

Light's AI workforce handles accruals, receipt matching, bank reconciliation, and close memos on top of clean billing data. Policies decide what runs on its own and what needs a human

Billing runs in a subscription tool that handles 60 to 75% of the pricing model; the rest lives in spreadsheets and manual invoices

Solvimon bills the full model (subscriptions, usage, credits, commitments), and every invoice lands in Light

Finance exports invoices and builds journal entries by hand, per entity, at month-end

Journal entries post to Light's ledger as transactions happen, entity-mapped, with intercompany eliminated at group level

Parent-entity commitments and child-entity usage are reconciled manually

Roll-ups are configured per customer once and reconcile on every billing run

Collections status is tracked in 2 systems that never agree

Card and direct debit collections run in Solvimon; bank-transfer invoices are chased in Light; paid status syncs both ways

Close is a project: reconcile, accrue, explain variances, write the memo

Agents reconcile continuously and draft the close memo; the team reviews exceptions