Electronic invoicing·Reactive Move

From invoicing every payment by hand to an adapter that issues the electronic invoice on its own.

How Reactive Move connected its appointment scheduler to SIIGO and gave its accounting team 4 full days a month back, on USD 3 a month of infrastructure.

Client
Reactive Move
Industry
Electronic invoicing
Size
1,000+ invoiceable payments a month
Counterpart
Accounting team
Duration
3 weeks
Service type
AI Factory: reusable integration adapter (webhook → validation → SIIGO) deployed on Google Cloud
100%of electronic invoices issued automatically
32 ha month of accounting work recovered
USD 3a month of infrastructure on Google Cloud

The problem

Reactive Move invoices every payment that comes in through its scheduling platform, AgendaPro. With more than 1,000 payments a month, someone in accounting had to take each payment, create or update the customer in SIIGO (Colombia's accounting and e-invoicing platform) and issue the electronic invoice with DIAN, Colombia's tax agency, one at a time.

That work consumed about 4 full days a month, 32 hours, of the accounting team's time. At a reference salary of USD 750 a month (COP 3,000,000), that was roughly USD 150 a month, more than USD 1,800 a year, spent copying data from one platform to another instead of doing the company's accounting.

And because everything passed through human hands, the process carried the usual problems of manual data entry:

  • Invoices issued late or never issued when volume went up.
  • Typing errors in ID numbers, amounts or taxes that later had to be corrected with DIAN.
  • Zero traceability: nobody could say for sure which payment had already been invoiced and which had not.

What we built

We built an integration adapter that connects the appointment scheduler to SIIGO and issues the electronic invoice on its own. Every time a payment is recorded, a webhook (payment.created) triggers the flow: we validate that it is a real payment with an amount greater than zero, normalize the data (ID number, taxes, service and salesperson), authenticate with SIIGO, create or update the customer and generate the electronic invoice, with nobody touching a keyboard. We designed it as a reusable piece: the same adapter can connect other scheduling or payment platforms to SIIGO.

  1. 01
    Webhook intake: the scheduling platform notifies each payment and the system picks up the data automatically, with nothing exported or uploaded by hand.
  2. 02
    Validation and sanitization: confirms it is a real payment with an amount above zero and normalizes ID number, taxes, service and salesperson before invoicing.
  3. 03
    Electronic issuance in SIIGO: authenticates, creates or updates the customer and issues the electronic invoice with DIAN, with no manual data entry.
  4. 04
    Error handling with alerts: if SIIGO rejects something (customer record missing, fiscal year closed), the system emails the details for review instead of losing the invoice silently.

Everything runs on our own infrastructure on Google Cloud instead of a subscription service, with a static IP so the webhook never drops and memory tuned for the free tier. Result: the cost of running the automation came down to about USD 3 a month.

The result

01

100% of electronic invoices issued on their own

From each payment in the scheduler to the electronic invoice in SIIGO with no human intervention. The accounting team stopped copying data from one platform to another.

02

4 accounting days recovered a month (about USD 1,800 a year)

The 32 hours a month that went into manual invoicing came back to the business. At the reference salary, that is about USD 150 a month, more than USD 1,800 a year (COP 7.2M), freed up for higher-value work.

03

USD 3 a month of infrastructure

We moved the flow from a subscription service to our own deployment on Google Cloud's free tier. The monthly cost of running the automation settled at about 3 dollars.

The system from the inside

Reference images of the delivered product. The data shown is illustrative and does not correspond to real client or operational information.

The Forabi Method

  1. 01
    Free consultation

    We mapped the manual payment-by-payment invoicing process and where hours were lost and errors slipped through to DIAN.

  2. 02
    Design

    We defined the validation rules and the data mapping between the scheduler and SIIGO, treating the adapter as a reusable piece rather than a one-off patch.

  3. 03
    Build

    We implemented the webhook → validation → SIIGO flow (auth, customers, invoice) with email error handling, and deployed it on Google Cloud with a static IP and tuned memory.

  4. 04
    Adoption

    We moved invoicing from the manual process to the automatic one and left the accounting team with only the cases that need review.

  5. 05
    Ongoing support

    We monitor issuance, adjust rules when DIAN or SIIGO change, and reuse the adapter whenever a new integration comes up.

Is your operation growing faster than your tools can measure it?

Book your free consultation
Reactive Move · Case study · forabi.ai