Fintech development · Assessment
Payment and billing software that reconciles to the cent
Remittance, invoicing or billing software gets a two-week review, then the work it calls for. We have built payments for five products in four markets.
FormatWritten assessment
Timeline2 weeks for the review
PricingFixed-price assessment · hourly work
Proof3 case studies
The assessment in 4 parts
01 · Signs you need it
If two of these apply, this is a good fit.
- The invoice and the database disagree by a few cents
- Stripe doesn’t work in your market
- An issued document can still be changed afterward
- Billing, renewals and reminders depend on someone remembering
- A payment went through with the wrong amount, and the system carried on as if it were right
02 · What you get
The review checks your system on four points, and the build that follows fixes the ones that fall short:
- Amounts stored as integers in the smallest currency unit, from the database to the invoice, so two screens never round the same amount differently.
- Issued documents that stay frozen. A correction is recorded separately, and the original stays readable in its issued form.
- Billing, renewals and dunning as scheduled jobs that apply one rule to every account. Nothing sent from staging can reach a real customer.
- A payment provider chosen for each market, with a local gateway where the global ones don’t work, and failed payments and retries handled as part of the product.
03 · How we decide
STEP 01Amounts are stored as whole numbers.We never use floating-point numbers where money is involved.
STEP 02Creating a document doesn’t make it valid.On a remittance terminal, a coupon printed without a network exists, but it can’t be paid out until the system validates it.
STEP 03We choose the payment provider by market.It has to work where your customers pay. In two of our integrations, regulation decided the partner.
STEP 04Service follows the amount received.Duration and entitlement are calculated from what actually arrived, so a wrong payment shortens the service instead of making it free.
04 · If we find nothing
The document confirms that your amounts reconcile and lists the places where they would stop reconciling as volume grows.
Proof
Where we’ve done this before
Case study 18 · Business systems4 marketsPayment integrations for five products in four markets, from Stripe and PayPal to a national government gateway in West Africa and a domestic gateway in Bosnia and Herzegovina.Read the case study →Case study 11 · Identity3 domainsCustoms invoicing, remittance terminals and a meetings platform, each built to keep the moment a document is created apart from the moment it becomes valid.Read the case study →Case study 07 · Marketplace6 jobsSix daily jobs that handle renewals, downgrades, dunning and reminders for a US marketplace.Read the case study →
FAQ
Questions about this service
Yes, including in the Balkans and West Africa.
We freeze the rate at the moment of payment. An invoice that has been issued but not yet paid takes the rate of the day it is settled.
The system records them. We build the part that has to reconcile, and the bookkeeping stays with your accountant.
Yes. Most of this work is done around the provider you already use, without a migration to another one.
With the two-week review of what you have. If building is needed, we agree on it afterward, based on what the review found.
Next step
Describe the problem and we’ll come back with three options.
The first call takes 30 minutes, and you’re under no obligation.