PHC ERP Integration

The Problem

Why does this extension exist?

A Portuguese operator has to issue certified invoices with a valid ATCUD and QR code, and report them in SAF-T. If your charging platform and PHC do not talk to each other, somebody re-types every charge detail record into the ERP at month end. It is slow, it is where the errors come from, and sessions quietly go unbilled — which is revenue you earned and never invoiced.

The Solution

What you get

Every closed CDR becomes a document in PHC through the Cegid PHC REST API, with no manual export
Customer records created in PHC or matched to an existing one from the driver's billing data, including the tax number
Portuguese tax rules applied per line: VAT rate, exemption reason, and the energy tax where it applies
Certified numbering stays in PHC, so ATCUD and the invoice QR code come from the certified program
Invoice PDFs returned to OASIS HUB and shown to the driver in the app and the customer portal
Automatic retry with backoff on failure, and a per-document log of exactly what was sent and what came back
Credit notes for refunded or corrected sessions, linked to the original document

🎯 Who is this for?

Portuguese CPOs and eMSPs that already keep their accounts in PHC (Cegid) and want charging revenue in the ledger the day it is earned, not the month after.

Enable This Extension Browse All Addons

🔌 Modular by design

Enable or disable per tenant. Pay only for what you use. All addons integrate seamlessly.

Key Capabilities

Everything included

CDR to Invoice

Every closed charge detail record becomes a PHC document. Energy, time and the other tariff components are carried across as invoice lines, so the invoice explains itself.

Customer Sync

Drivers and fleet companies are created in PHC or matched to an existing record by tax number, so the same customer never ends up in the ledger twice.

Portuguese Tax Handling

VAT rates, exemption reasons and the energy tax are applied line by line under Portuguese rules, ready for SAF-T reporting.

Certified Numbering

Document numbering, ATCUD and the invoice QR code are produced by PHC. The certified program stays the source of truth — OASIS HUB never invents a number.

PDFs in the Driver's Hands

The invoice PDF issued by PHC comes back to OASIS HUB and appears in the driver app and the customer portal, with no email chase.

Failures You Can See

Every call is logged with its payload and its response. Failed documents retry on their own and stay on a list until they clear.

Use Cases

See it in action

How operators around the world can use this extension to solve real problems and grow their business.

Month end without a spreadsheet

Two thousand four hundred sessions closed in March. Each one already carries a PHC invoice with its own number and QR code. The accountant opens PHC and finds the month closed, instead of importing a CSV and reconciling it.

A fleet customer with one invoice per site

A logistics company charges at four depots. Billing groups the month's CDRs by cost centre and PHC issues one document per site, with every session itemised underneath.

A corrected session, corrected properly

A session was billed on the wrong tariff. The correction issues a credit note in PHC linked to the original invoice, and the driver sees both documents in the app — no manual note, no orphan entry.

Simulated Case Study

Portuguese CPO closes the month in PHC in one afternoon instead of six days

An operator with 180 chargers issued invoices by exporting CDRs to a spreadsheet and typing them into PHC. Closing a month took two people six working days, and roughly 3% of sessions were never invoiced at all. After connecting PHC, invoices are issued as sessions close. The month is now reviewed in a single afternoon and unbilled sessions fell to zero.

Sessions left uninvoiced

6 days

Of manual work removed monthly

180

Chargers billed automatically

< 1 min

From session end to invoice

PHC (Cegid) ERP Integration