Cami × CrossVal · Embedded accounting
The groomer didn’t sign up
to become an accountant.
She opened at seven and she is still here at ten, because the VAT return is due and the books will not
line up with the bank. It is the hardest hour of her week, and it happens to be the one part Cami cannot
help her with yet.
What the operator is up against
Two new mandates,
and one old mess.
PAIN 01
VAT & corporate tax
5% filed every period, 9% now live. Miss it and the penalty lands on the owner.
PAIN 02
E-invoicing
Every booking must become a structured, reportable invoice. A PDF will not pass.
PAIN 03
The books never agree
Bookings in Cami, money in the bank, a bookkeeper on WhatsApp stitching it after the fact.
The move
Cami stays in front,
CrossVal works behind it.
A booking is paid in Cami. CrossVal, UAE-native and filing straight to the
FTA, issues the compliant e-invoice, posts the entry and prepares the return. The operator never meets it.
They just see Cami, finally finishing the job.
CAMI EVENT
Booking paid
groom, boarding, retail
→
CROSSVAL POSTS
Ledger + e-invoice
revenue, 5% VAT output
→
RESULT
FTA-ready
return prepared, books closed
The obvious question
Why not just wire Cami
to Xero or QuickBooks?
Because a connector moves the data and leaves the problem.
The operator still buys, learns and logs into a second tool, and someone still has to make a general ledger
understand pet care.
A connector to Xero or QuickBooks
- The second subscription stays, and so does most of the ~$78
- Raw sales rows land in a generic ledger that a bookkeeper still configures for packages, tips and deposits
- The finance revenue and the relationship go to the accounting vendor
- No UAE e-invoicing or corporate tax filing to the FTA
CrossVal embedded in Cami
- Nothing new to buy, learn or log into, because it lives inside Cami
- The pet-care mapping is built in once and applied to every operator correctly
- The finance line is Cami’s revenue, priced at wholesale
- UAE-native rails issue compliant e-invoices and file to the FTA
What we can ship, and when
Two versions of
the same story.
The endpoints Cami shared are the sales side: invoices, revenue lines already carrying per-line
VAT, refunds, cancellations. That alone ships the sharpest pain, with no new data pipes. CrossVal’s
direct APIs then add the half Cami does not hold, so think of them as two steps in order rather than a choice
between them.
Version 1 Ship now
Built from Cami’s endpoints alone.
This is the order-to-cash compliance layer, and every card
below uses fields Cami already emits, so it ships without a single new data pipe.
V1.1
FTA e-invoice at point of sale
from: invoice_id, merchant vatNumber, customer_id, line items, per-line taxAmount, inclusive/exclusive flag
V1.2
Output-VAT return prep
from: Sale taxTotal, taxAmount, TaxRule; less refund_amount where refund_status = captured
V1.3
Revenue P&L by service & location
from: subtotal, discount, total, taxTotal, service_name, merchant_id, issue_date
V1.4
Credit notes, VAT reversed right
from: refund_id, original_invoice_id (parentSaleId), refund_amount, refund_status
V1.5
Compliance & cancellation flags
from: vatNumber gaps, inclusive/exclusive mismatch, refund vs total, audit-log cancelled_at
V1.6
Revenue dashboard & forecast
from: total, paid_at, issue_date, service_name, merchant_id
The honest line
Where Version 1 stops.
These endpoints are pay-at-point-of-sale and revenue-only. On their own,
four things stay out of reach, and the fields tell us exactly why.
Not possible from Cami alone
Net VAT payable no input VAT from purchases
Full P&L / profit no COGS, expenses or payroll
Bank reconciliation channel detail lives in NeoPay, not Cami
Package & tip liabilities a package is only a customer_package payment
That boundary is the whole reason Version 2 exists, and crossing it is exactly what the direct APIs are for.
The money going out
Cami captures every sale,
and none of the spend behind it.
The costs that keep a grooming or boarding business running
never touch Cami: the rent, the wages, the food and shampoo, the vet supplies, the payment and software fees.
That spend is the operator’s real cost base, and today it lives in a drawer of receipts and a banking app.
Food & stock
books as cost of sale
Rent & utilities
books as operating expense
Staff wages
books as payroll
Grooming supplies
books as operating expense
Payment & software fees
books as operating expense
CrossVal captures it from
uploaded bills & receipts
the bank feed
recurring costs
Once the spend is in the books
the rest follows: input VAT to reclaim, a true cost of sale, real profit instead of turnover, and the base the 9%
corporate tax is actually charged on.
Version 2 Direct API
CrossVal’s direct APIs
finish the job.
Cami’s events join CrossVal’s ledger, bank feeds
and filing, and the picture is complete.
V2.1
Net VAT return, filed to the FTA
adds: purchase & expense capture, input-tax records, FTA submission
V2.2
Full P&L and balance sheet
adds: purchase ledger, expenses, payroll, chart of accounts
V2.3
Corporate tax, computed & filed
adds: IFRS financials, tax adjustments, FTA corporate-tax filing
V2.4
Bank & NeoPay reconciliation
adds: bank feeds, NeoPay settlement join, gateway fees
V2.5
Deferred revenue & liabilities
adds: liability accounts, redemption & payout logic on the ledger
V2.6
Ledger, multi-entity, AI assistant
adds: general ledger, multi-location consolidation, ask-the-books
What Cami sells
Compliance first,
then everything else.
BASIC · V1
Stay compliant
E-invoice on every booking, FTA-ready VAT, automated books and P&L.
BASIC + · V1+V2
See the business
Cash flow, revenue by service and location, utilisation, forecasting.
BASIC ++ · V2
Ask the books
AI finance assistant and automated corporate tax filing.
Once the ledger runs inside Cami, the same rails can carry payments, lending and insurance later, and
each of those is a new revenue line rather than a fresh build.
The economics
The operator pays less
while Cami earns more, every month.
TODAY
~$78
a booking tool plus a separate accounting stack, reconciled by hand
→
WITH CAMI
one bill
compliance bundled below that number, second tool retired, wholesale from CrossVal
→
THE RESULT
margin × locations
a finance line on every location, compounding as operators grow
Exact price points are what Stage 0 locks, alongside the wholesale rate card.
The plan
Stage 1 is Version 1.
Stages 2 and 3 grow into Version 2.
Stage 1 ships the e-invoicing and output-VAT layer from Cami’s shared endpoints, live with 5 to
10 grooming and boarding operators. Stages 2 and 3 wire in the direct APIs: net VAT and corporate tax, bank
reconciliation, liabilities, the AI assistant, then payments and lending.
The ask
Give us Stage 0, and four
weeks later we will know.
CrossVal bringsthe embedded API and sandbox, proof of FTA and e-invoicing coverage, a draft wholesale model
Cami bringsthe shared endpoints and a pilot cohort of 5 to 10 grooming and boarding operators
Together we lockthe event-to-books mapping, signed off by a qualified accountant, and the terms
Own the compliance, and you own the wedge.
1 / 13