By Appbay Technologies
A facility signing makes the headline. Tagging, evidencing and reporting every loan under it is the work that follows.
An Egyptian bank is expanding SME lending under a risk-sharing facility with a development finance partner, intended to widen access to finance for small and medium businesses while sharing part of the lending risk. A named facility with stated social aims signals intent. It also raises a practical question: behind every loan the bank approves, how many extra checks, tags and reports does each one still have to go through?
This piece is a candid one. The fit is a good one with some configuration work, and we’ll be specific about which parts are which.
The Priority: More Lending to Small Businesses, With Shared Risk
Expanding SME lending under a risk-sharing facility is a clear and worthwhile priority. It supports small and medium businesses that are often under-served, it gives the bank room to lend with part of the risk shared, and it carries a social purpose that goes beyond the loan book: jobs supported, women-led businesses reached, and similar outcomes the facility’s partner expects to see.
That purpose is part of the deal. The facility terms attach extra tagging and reporting to ordinary SME loans, so the bank is expected to show not only that it lent, but who it reached and what followed.
That creates a real operational question: does each loan under the facility follow a single journey, from application to decision to evidence, or does the same file get handled again by several teams after it has been approved?
The Hidden Problem: One Loan, Two Jobs
Normal underwriting still applies. Then the facility adds a second job on top of it.
Here’s where the operational gap can show up, inside a bank lending under a risk-sharing SME facility:
- Eligibility checked case by case – each application is matched to the facility’s criteria by hand at underwriting, rather than inside the workflow
- Impact data chased afterwards – jobs, women-led businesses and other claims collected for each reporting period, long after the loan was approved
- Programme team assembling reports – finance, sustainability and the facility manager pulling figures from several places by hand
- Eligible loans missed or late-tagged – a loan that is not tagged when it is written may never be counted against the facility
The people who feel this first are SME underwriters, credit operations, the facility or programme manager, and the finance and sustainability reporting teams. The budget owner is usually the Head of SME or the COO, with the CRO involved because every decision still has to stand as a credit decision.
Why does this exist? Facility terms were written after the SME lending process already existed, so the checking and the evidencing sit beside the loan journey instead of inside it. The bank underwrites normally, and then separately works out which loans qualified and what they achieved. When eligibility is assessed case by case and impact data is gathered after the fact, the same file is handled several times, reporting is assembled late, and impact claims are hard to trace back to individual loans.
Why This Matters Now
The facility was signed. How much of it has reached eligible businesses?
The board backed the facility. It now wants utilization and cost per eligible loan on the next pack. The question that follows isn’t rhetorical:
“The facility was signed. How much of it has reached eligible businesses, and what did each loan cost to evidence?”
For the Head of SME, the COO and the CFO, this plays out across four measures:
- Facility utilization versus plan – how much of the facility eligible borrowers have actually used
- Cost per eligible loan – what each loan costs to underwrite, tag and evidence once review effort is counted
- Eligible loans missed or late-tagged – how many qualifying loans were not captured when they were written
- Partner reporting on time – whether reports reach the development finance partner when due, with figures that trace back to individual loans
There is also a wider expectation. Impact claims such as jobs supported and women-led businesses reached have to be evidenced, not estimated, which brings the Head of Sustainability into the same conversation as the credit team.
Without that visibility, the facility widens SME lending on paper, but utilization, cost per eligible loan and reporting quality stay where they were, so the benefits of the facility are hard to show and easy to under-use.
An Honest Look at the Fit
We want to say this plainly: this is a good fit, with configuration work. SME loan origination and approval sits in Appbay’s core strength. Appian is built for orchestrating work across teams: intake, risk-tiered routing, approval, and audit trail.
What transfers directly:
- Document intelligence for SME files
- Audit IQ-style auditable reporting for every decision
- LoanSphere, our origination, processing and decision workflow, for the SME loan journey
What is configuration work, not a ready product:
- The facility’s own eligibility criteria
- The impact data fields the bank needs to capture
- Any reporting template the development finance partner requires, which the bank and the partner have to define together
Credit decisions, risk appetite, and what is reported stay with the bank. AI supports the analysis and does not make the call.
Here’s what that would actually involve:
Capture the SME Application
One governed workflow from application to decision, instead of a separate eligibility exercise afterwards.
AI Extraction and Eligibility Checks
Files checked as they arrive against the facility’s criteria, with gaps flagged before the application moves on.
Auto-Route by Risk and Eligibility
Each application reaches the right officer with the evidence already assembled, so simple files clear quickly and complex ones get the right attention.
Credit Officer Decision
Every credit decision remains with a person.
Audit Trail and Impact Data
Every step and decision on record, with the eligibility tag and impact fields captured together with the loan.
The practical starting point is a scoped 8-12 week proof of concept on one SME loan product under the facility. It would show whether checking eligibility at origination, and capturing impact data with the loan, lightens reporting without slowing underwriting. It would not cover every SME loan, and extending it would be a larger conversation about scope.
Why We’re Saying This Plainly
Being specific matters more than a broad claim would. This problem sits close to what Appbay already builds, so the honest message is that we can scope it clearly, and that the eligibility criteria, impact data fields and partner reporting template are configuration work that depends on how the facility has been defined. Naming that up front is more useful than overstating it.
This Pattern Isn’t Unique to One Bank
Any institution lending under a risk-sharing or development-backed SME facility will face the same constraint: normal underwriting still applies, but each loan also has to be matched to eligibility criteria and reported on later. The banks getting ahead of this check eligibility at origination, capture impact data with the loan, and keep a person deciding, so the facility lowers the cost of reaching eligible businesses and doesn’t just add a reporting burden after the fact.
Let’s Compare Notes
We’re curious how other banks are evidencing eligibility and impact on SME facilities without slowing underwriting. If your organization is working through the same challenge, we’d welcome the conversation.
Send us a message at sales@appbaytech.com or visit www.appbaytech.com. This one’s genuinely about comparing notes, not a pitch.


