Skip to content
OpeniDevelopers

CasesUrban mobility

Reimbursement of Rio de Janeiro's transit operators

Riocard automated the reimbursement flow for the transit operators of the state of Rio de Janeiro. Bank movements arrive through Open Finance, are reconciled against the amounts owed to each operator and the result goes to SAP. The operation also runs 150,000 tax invoices a month through Docs.

Riocard Mais
Request accessDocumentation

From source data to result

  1. 1Open Finance
  2. 2Reconciliation
  3. 3Reimbursement
  4. 4SAP
tax invoices per month
150K

The challenge. Urban mobility.

In electronic ticketing, the passenger tops up the card once and rides buses, trains, ferries and light rail run by different operators. Each trip generates an amount to reimburse to the operator that provided the ride. Finance has to make sure the amount calculated for each operator is what actually left the bank, on the right day, and record it all in the ERP. With many operators and recurring transfers, checking this line by line does not close on time.

Calculated reimbursement and bank statement
Example
Amount owed per operatorStatement (Open Finance)

  • Operator A

    R$ 184,320.00

    Checked

    TED sent

    R$ 184,320.00

  • Operator B

    R$ 97,510.40

    Checked

    Pix sent

    R$ 97,510.40

  • Operator C

    R$ 61,200.00

    Mismatch

    TED sent

    R$ 61,020.00

  • Operator D

    R$ 45,870.15

    No credit

    no pair

Sample data, to illustrate the flow.

How it works. In 3 steps.

  1. 01

    Bank movements arrive through Open Finance

    The transactions of the accounts used for reimbursement are read straight from the bank, with consent, with no statement downloaded by hand.

  2. 02

    What is owed is compared with what was paid

    The amounts calculated per operator come in as the other source. The rule set matches each transfer with the corresponding bank credit.

  3. 03

    The result goes to SAP

    What checks out is recorded in SAP. A transfer with no credit, a different amount or a movement with no operator is set aside for the team.

How it runs through the API. In documented calls.

  1. GET /v1/items/{itemId}/accounts/{accountId}/transactions

    Open Finance returns the transactions of the connected account.

  2. POST /v1/rule-sets/{ruleSetId}/run

    The rule set runs and matches the two datasets.

  3. GET /v1/matches

    Each pair comes back with a decision and a score.

What stays visible. Set apart for the people who operate.

  • Transfer with no matching bank credit
  • Credited amount different from the amount owed
  • Movement with no operator identified

Other cases

“We integrated Open Finance in one sprint. The documentation answers before we need to ask.”
Marina DuarteHead of Engineering, credit fintech
“The reconciliation that took the team two days now runs on its own.”
Rafael AntunesCTO, retail chain

Teams from fintechs, retail and accounting already integrate with Openi.

Request access

Build your reconciliation. With the same calls.

The cases use documented endpoints only. Request access and run the flow with your own operation's data.

Request accessDocumentation