Back office

One back office for every team, on the same data.

Credit, collections, treasury, risk, accounting and compliance each get their own workspace, with their own permissions and the same live numbers. No spreadsheets in between, and every change recorded.

Seven areas, one for each team

The back office isn't one generic inbox. It's the full operation of a financial institution, organized by area, where each team works in its own space with its own permissions and workflows.

Who uses itOrigination, credit analysis, loan book and collections teams

ApplicationsApprovalsGuaranteesRevolving creditThe loan bookAgeing of the loan bookCollections

Who uses itTreasury

Payouts in batchesReconciliation of every movement

Who uses itRisk

Provisions under local rulesIFRS 9

Who uses itSavings and deposits teams

Savings accountsTransfers to other banks

Who uses itAccounting

MovementsAccrualsThe chart of accountsFinancial statementsPeriod close

Who uses itThe compliance officer and anti-money-laundering team

Credit bureau reportingCash transaction reportsSuspicious activity reports to the financial intelligence unit

Who uses itPlatform administrators, business and risk leaders

Approval rulesCredit scoringTwo-person approvalGuarantee typesWorkflowsPayment gatewaysIntegrationsBrandingUsers

From the first click to the last payment collected

Applications, guarantees, payouts, the loan book and collections in one place. Less time per application, better control of late payments, and a full record of every decision.

Application

Every request arrives with the customer's details, documents and identity checks.

Guarantees

Collateral and co-signers are registered against the loan.

Approval AI

Your approval rules run, with credit scoring support from AI; above a set amount, a second person approves.

Payout

The money goes out through treasury, in batches or one by one.

Loan book

Every loan's status, balance and days late, live, grouped by how late payments are.

Collections AI

Collection lists ranked by likelihood of payment, with early warning when the loan book starts to deteriorate.

See loan products

The books always match the operation

Payouts, reconciliation, provisions under the rules, and full accounting with financial statements and period close. What usually takes several systems runs on one here, so what happens in the product is what lands in the books.

Today's reconciliation

99.5%

AI6 items to match

Payouts in progress

318 of 318

Complete

Financial statements

Assets = L + E

Balanced

Provisions

IFRS 9

Recalculated today06:00

Sample data from the product, not client results.

  • Payouts

    Loan payouts go out in batches from treasury, tracked one by one.

  • Reconciliation

    Every movement is matched automatically; AI flags the items that don't match.

  • Provisions

    Calculated under local rules and IFRS 9, always in step with the loan book.

  • Accounting

    Movements, accruals, financial statements and period close, recorded as the operation happens.

  • Alerts AI

    Movements outside the expected pattern are flagged for review.

Reports to regulators come built in, not bolted on

Credit bureau reporting and anti-money-laundering reports run from the same data as the operation, with full traceability and support for audits. They are ready for Colombian rules and set up for other countries during implementation. Compliance stops being a project on the side and becomes part of the everyday operation.

  • Credit bureau reporting

    Generated from the loan book, on schedule.

  • Cash transaction reports

    Built from the movements already recorded.

  • Suspicious activity reports

    Prepared for the financial intelligence unit, with the evidence attached.

  • Unusual operations AI

    AI flags unusual operations and suggests which ones may need a report, so your team spends its time analysing, not searching.

  • Audit trail

    Every review, decision and report is recorded.

See security details

Change rules, products and branding without writing code

Approval rules, credit scoring, guarantee types, workflows, payment gateways, integrations and branding are all set from the back office. Launching a product, changing a risk policy or switching on a connected provider stops being a ticket for developers and becomes a setting, with a second person's approval where it matters.

  • Approval rules

    Decide who qualifies and for how much, in plain conditions.

  • Credit scoring

    Adjust the scorecard your approvals use.

  • Two-person approval

    Sensitive changes are made by one person and approved by another before they go live, and the change is logged for audit.

  • Workflows and guarantees

    Set the steps of each process and the types of guarantee you accept.

  • Connected providers

    Switch on payment gateways and integrations that are already connected.

  • Branding and users

    Update your brand and manage who can do what.

  • Suggestions from AI AI

    AI suggests adjustments to rules and scorecards based on how your loan book is behaving.

New integrations and regulatory changes still go through technical review.

See what your team can change alone

Questions about the back office

Yes. Access is set by role, so each team sees and does only what its permissions allow.

Yes. The back office can run on top of the core you already have, or on the Cowally core.

Yes. Each area works on its own, so you can start with one and add the rest later.

Credit bureau reporting and anti-money-laundering reports are built in for Colombia, and provisions follow local rules and IFRS 9. Other countries' requirements are set up during implementation.

Yes. Reports are ready to export.

Yes. AI services are switched on per client and billed by use.

See your team's day in the back office

In one session we'll walk through the areas your teams use every day, running a product like yours.

Which describes you?

We reply within one business day.