Frequently asked questions

MetrikData is bank statement analysis software for merchant cash advance underwriting. It reads business bank statements, detects financing positions and MCA stacking, calculates debt burden against external revenue, and verifies statement authenticity. Every figure ties back to the underlying transactions, so brokers, ISOs, and funders get a clear, auditable view of repayment pressure in seconds. MetrikData surfaces the data and the supporting evidence — the underwriter applies their own criteria and makes the decision.

MetrikData reads PDF bank statements from every major US bank, including Bank of America, Chase, Wells Fargo, TD Bank, Citibank, US Bank, Capital One, PNC, and Truist. Text is read directly from the PDF rather than scraped from screenshots, so transactions, balances, and dates are extracted accurately. Each transaction is cleaned up and categorized automatically, and you can review the extracted data before running an analysis to make sure the inputs are correct.

MetrikData groups transactions by payee to identify recurring funder withdrawals, then separates merchant cash advances from term loans so debt service is categorized correctly and stacking counts are not inflated. Retail and point-of-sale activity is excluded so it never reads as a financing position. Debt burden is calculated against operating revenue with own-account transfers and new advance receipts removed, so the burden percentage reflects actual obligations against real revenue rather than total inflow. This is how MetrikData surfaces a more accurate stacking and burden picture than keyword-only tools.

External revenue is operating revenue with own-account transfers and new financing advances removed from the denominator. It matters because advances from funders are not operating revenue — including them inflates the revenue base and understates how much real income is already committed to existing positions. By calculating burden and concentration against external revenue, MetrikData gives underwriters a truer read on repayment pressure and avoids the optimistic distortion that simpler, keyword-based tools produce.

As each PDF is parsed, MetrikData checks it against several independent tamper signals: editing-software traces in the metadata, whether beginning balance plus credits minus debits reconciles to the ending balance, created-versus-modified timestamps, and font consistency across the document. Each signal resolves on its own and every flag points back to the document itself, so a doctored balance or a re-saved file is surfaced before it reaches underwriting. MetrikData flags the signals for review; it does not claim certainty of fraud.

No. MetrikData is not a decision engine and does not approve or decline deals. It surfaces positions, debt burden, cash-flow signals, authenticity flags, and a risk summary, with every metric tied to the transactions behind it. The underwriter reviews that evidence and applies their own guidelines to reach a decision. This separation is deliberate: MetrikData provides the analysis and the audit trail, and the lending decision stays with the people accountable for it.

Uploaded statements are processed to produce your analysis and are stored privately against the merchant record so you can revisit reports, processing status, and exports. Retention periods, storage location, and access controls are described in the MetrikData privacy policy. Data handling is built around keeping each workspace's statements private to that workspace.

No. Statements you upload are used to generate your analysis and are not used to train AI models. Your merchant data stays within your workspace and is not repurposed for model training.

MetrikData is built for the US merchant cash advance market — funders, ISOs, brokers, and underwriters who review business bank statements as part of their workflow. It fits teams that want faster statement analysis with reviewable formulas and an audit trail, rather than a black-box score. The same engine is designed to extend to adjacent use cases such as CPA review, SBA, landlord screening, and factoring over time.

MetrikData offers a free trial so you can run a full merchant before paying, plus paid plans for individual underwriters and teams. Every workspace starts with 10 free credits and no credit card required — a typical bank statement costs 1 credit, and long or scanned statements cost more. See the pricing page for current plans, monthly credit volumes, credit packs, and team seats, all in USD.

Completed analyses can be exported as clean underwriting reports in PDF and CSV, so you can share the picture with a credit team or attach it to a file for record-keeping. Exports stay tied to the merchant record alongside the original statement and its processing status, which keeps the workflow audit-ready.

Yes. You can review the normalized transactions and correct anything before running an analysis, so the resulting burden, positions, cash-flow signals, and risk summary are built on accurate inputs. Because every figure links back to its source rows, corrections are transparent and easy to verify.