Use cases
Who uses Kederi, and for what
A Nigerian bank statement is mostly free text. Each team that reads one needs a different answer from it. These pages show four of those teams, the rows they send, and what comes back.
The people, accounts and references in the examples are invented, and none of them belongs to anybody. The businesses are real merchants in our directory. A test runs each example through the engine and fails if a page and the engine disagree.
Lenders and loan teams
Read an applicant's statement: which credits are salary, which are the applicant's own money moving between accounts, and which debits repay another loan or go to betting.
Accounting and audit
Turn a client's statement into named payees, bank charges by type, and recurring bills, so fewer rows need a person to post or check them.
Expense and business banking
A transfer has no merchant. Kederi returns the party and the purpose that the sender typed, so the row can go to a category without a person.
Compliance and screening
Get the person's name out of a transfer narration, so a screening tool compares one name and not the bank, the rail and the reference too.
Try it on your own rows
The playground reads one narration with no account. With an account, the console reads a CSV, OFX or QIF statement in your browser and sends only the rows to the API.
Sign up