01
One file
The application and the statements stay together. Account numbers are stored as the last four digits.
For funders and underwriting teams
The deal file, with the lines behind it.
Credalane keeps the application and the bank statements in one file. It separates true revenue from transfers and funding, and it shows the statement line behind each figure. An underwriter makes the decision.
What the file shows.
The same figures an underwriter checks, each one tied to the lines it came from.
02
True revenue
Deposits are not all revenue. Transfers, funding, returns, and refunds are left out, and the file shows those lines.
03
The statement lines
Open a finding and the lines it came from are right there, with the page they were read from.
04
Positions
A recurring pull is listed as a position. A name cut short on the statement does not hide it.
05
Three counts, kept apart
NSF days, days that end below zero, and bounced pulls are each counted on their own.
06
Statements that connect
Opening, credits, debits, and closing are checked, and each month is checked against the next.
A file, opened.
This layout is the file. The names, dates, and amounts are example data, not a customer.
All deposits
$42,500.00
Left out
$6,200.00
True revenue
$36,300.00
Jun 3
Card deposit
$20,000.00
Counted
Jun 8
Transfer from the business's own account
$4,000.00
Left out, transfer
Jun 12
Transfer from the business's own account
$2,200.00
Left out, transfer
Jun 21
Card deposit
$16,300.00
Counted
| Date | Statement line | Amount | How it is read |
|---|---|---|---|
| Jun 3 | Card deposit | $20,000.00 | Counted |
| Jun 8 | Transfer from the business's own account | $4,000.00 | Left out, transfer |
| Jun 12 | Transfer from the business's own account | $2,200.00 | Left out, transfer |
| Jun 21 | Card deposit | $16,300.00 | Counted |
Finding
2 returned payments. Example dates: June 4 and June 18. statement_june.pdf, page 3, lines 14 to 19.
Show lines
Page 3, lines 14 to 19, in statement_june.pdf. Example dates: June 4 and June 18.
Suggestion
Needs review
A suggestion stays a suggestion. The words on the file say so.
Decision
Not recorded
An underwriter records the call here, in their own name.
A person makes the call.
Credalane suggests. The underwriter decides, and the file keeps who made the call.
- Suggest approve, Needs review, and Suggest decline are suggestions. Approved, declined, and held for review are decisions.
- When the decision differs from the suggestion, the person writes a reason.
- The team sets the rules. Each change is saved as its own version.
- A missing page, a scan that cannot be read, or a statement that does not reconcile goes to review. It is not called fraud.
Questions
- Who is it for?
- Funders and the people who underwrite their files.
- How does someone get in?
- Access is by invite. Sign in is for people who already have an invite. The link goes to the app at app.credalane.com.
- Who approves a deal?
- An underwriter. Credalane suggests, and the decision is a separate record.
- Is the sample file a customer?
- No. It is example data, so the layout can be shown without anyone's statements.
- What if the pages do not add up?
- The file goes to review, and the reason says so. A gap is not called fraud.
- Can statements be sent to this page?
- Statements belong in the app, for invited teams. This page does not take documents.