Line4

US Call Report checker

For US banks that file the quarterly Call Report: the FFIEC 031, FFIEC 041 and FFIEC 051. Line4 Check runs the FFIEC's own edits on your XBRL-XML file before you submit it to the CDR. Your file never leaves your computer.

LiveLine4 Check runs 1,632 of the 2,184 checks that apply to an FFIEC 031 report, 1,468 of the 1,928 for an FFIEC 041 and 1,096 of the 1,484 for an FFIEC 051, for the September 30, 2026 report date. Every check it runs is proven on test files against the CDR’s own specification. The rest are held back, and this page says why.

Drop your Call Report here

One XBRL-XML instance (.xml or .xbrl) of an FFIEC 031, 041 or 051 Call Report for the September 30, 2026 report date. The file is checked against the FFIEC's edits for the form its schemaRef names.

Your file never leaves your computer. It is checked inside this browser tab: nothing is uploaded, and nothing from the file is recorded.

The FFIEC does not publish sample reports, so the test files above are Line4's own: one per form, made from the FFIEC's taxonomy, with every item the checks read reported as zero, false or empty. They are not a bank's report, and some checks fail on them.

What we record

Your file is checked in your browser and never uploaded. This is all Line4 keeps about each check, here and on regulators’ websites that show Line4 Check.

For each check, Line4 records

  • Which Call Report form was checked and for which report date, such as FFIEC 041 for September 30, 2026
  • The file format: XBRL-XML
  • The kind of result: passed, warnings only, blocking errors, nothing could be checked, or a return not covered
  • The address of the page the check ran on, without anything after a ? or #
  • The date and time
  • Visits and clicks, counted by Vercel Web Analytics without cookies

Never recorded

  • Your file, or any part of it: it is checked in your browser and never uploaded
  • The file name
  • The entity, its LEI or the reporting date
  • Any value or message from the file, or which or how many checks failed
  • Who you are: no name, email, cookie or IP address is kept with the record

Your free checks: 10 a month

  • If you allow it, a small cookie on your device (l4_free) counts them. It holds only the month and the number, such as 2026-11.3, and lasts 35 days after your last check.
  • If you say no thanks, the cookie only remembers that. Our server counts your checks against a scrambled code made from your IP address and the month. The address itself is never kept, and the codes are deleted when the month ends.
  • A monthly total of free checks for each framework, with no link to you.

If you ask for the report by email, that report (not your file) and your email address are sent to Line4. See the privacy policy.

The three forms are in Line4's library of the FFIEC's returns, in plain English, with who files each one, when and in what format. Need premium support or bespoke validation, such as checks against last quarter's report? Contact us.

A check at submission is the first step to real-time supervision.

When a Call Report is checked the moment it is filed, problems are fixed while the figures are fresh, and what reaches the agencies is right when it lands.

That is what real-time supervision needs: validated data, sent straight from banks' systems, that supervisors can use as soon as it arrives. Line4 Check shows the first step on your own computer. For regulators, Line4 builds the rest.

What is real-time supervision? →Validation at the gate, for regulators →

Who files which form

US banks file the Call Report each quarter to the FFIEC's Central Data Repository (CDR), as an XBRL-XML file. Which form it files depends on its offices and its size.

  • FFIEC 031: Call Report for banks with foreign officesBanks of any size with any "foreign" office (an international banking facility, a branch or consolidated subsidiary abroad, or a majority-owned Edge or Agreement subsidiary). Banks with domestic offices only must also file it if they are advanced approaches institutions for capital purposes, or have total consolidated assets of $100 billion or more (measured each June 30 for the next year). National banks, state member banks, insured state nonmember banks and savings associations all file. (source; the FFIEC 031 in Line4's library)
  • FFIEC 041: Call Report for banks with domestic offices onlyBanks with domestic offices only and total consolidated assets under $100 billion, including Category III banks of that size but not advanced approaches institutions. A bank eligible for the shorter FFIEC 051 may choose to file the FFIEC 041 instead, and its supervisor may require it to. (source; the FFIEC 041 in Line4's library)
  • FFIEC 051: Call Report for smaller banks with domestic offices onlyBanks with domestic offices only and total assets under $5 billion (measured each June 30 for the next year), other than advanced approaches institutions, banks subject to Category III capital standards, and large or highly complex institutions for deposit insurance purposes. Eligible banks may file the FFIEC 041 instead, and the supervisor may require that for supervisory reasons. (source; the FFIEC 051 in Line4's library)

What it checks

The CDR runs three kinds of check on a Call Report. Line4 Check runs the same three, in the FFIEC's own words:

  • Validity edits. The CDR rejects a report that fails one. Line4 Check shows them as errors.
  • Quality edits. The CDR accepts the report, but the bank must explain each one that fails. Line4 Check shows them as warnings.
  • Sum checks. A total in the taxonomy must equal the items that make it up. Sum checks are shown as warnings, not errors. The CDR’s specification treats them as exact, but the CDR has accepted filed reports whose sums are off by a rounding difference.

The taxonomy for the September 30, 2026 report date carries 3,858 checks for the three forms together. A check applies to a form when it can run on that form's report for September 30, 2026. The others are for another form, or only for reports at other times of the year, and could only pass on yours: for the FFIEC 031, 1,485 are for other forms and 189 for other report dates.

  • FFIEC 031Banks with domestic and foreign offices. Proven on 53 test files.Checks run1,632of 2,184 · 74%Validity edits615 of 619Quality edits895 of 1,423Sum checks122 of 142Held back552
  • FFIEC 041Banks with domestic offices only. Proven on 44 test files.Checks run1,468of 1,928 · 76%Validity edits540 of 542Quality edits809 of 1,257Sum checks119 of 129Held back460
  • FFIEC 051Smaller banks with domestic offices only. Proven on 39 test files.Checks run1,096of 1,484 · 73%Validity edits386 of 388Quality edits628 of 1,006Sum checks82 of 90Held back388

Every report carries the same line, for example: “This free check runs 1,632 of the 2,184 checks that apply to an FFIEC 031 report for the September 30, 2026 report date: 615 validity edits, 895 quality edits and 122 sum checks, every one proven on test files against the CDR’s own specification. The other 552 do not run yet; line4.ai/call-report-validator lists them by reason. It is not a substitute for the CDR’s edits when you submit.”

What it does not run yet, and why

1,400 of the 5,596 checks that apply to the three forms, counted form by form, do not run yet. Line4 Check never counts a check it does not run as passed.

  • Needs last quarter’s report: 1,267The check compares this report with an earlier one, such as last quarter’s or last year’s. One file holds only its own quarter, so the check cannot run on it.FFIEC 031: 492; FFIEC 041: 421; FFIEC 051: 354.
  • Uses data the CDR works out itself: 76The check reads items the CDR calculates from its own records about each bank. A bank does not report them in its file, so the check cannot run on the file alone.FFIEC 031: 33; FFIEC 041: 23; FFIEC 051: 20.
  • Sums the taxonomy defines two ways: 38The taxonomy has two sums for the same total that add up different items, and it does not say which one is for this form. Neither runs until that is settled.FFIEC 031: 20; FFIEC 041: 10; FFIEC 051: 8.
  • Checks that cannot fail: 19The check tests that a yes-or-no item is either yes or no. Any yes-or-no item that is reported is one of the two, so no report can fail it, and a check is only run once it is proven to pass and to fail.FFIEC 031: 7; FFIEC 041: 6; FFIEC 051: 6.

Most of them compare this quarter with an earlier one. The CDR has your earlier reports; one file does not. If you want those checks too, tell us.

A report downloaded from the CDR's public site

The CDR publishes banks' filed Call Reports. A report downloaded from its public site always fails validity edit R0002.7523, because the public data leave out the vendor code of the software that made the report, and that edit checks the vendor code is there. Your own file, from your Call Report software, carries it. The other checks run on a downloaded report as on any other.

How the checks are proven

The FFIEC writes its edits in the CDR's own rule language, set out in the CDR Interchange Specification 2.18, not in the XBRL formula standard, so there is no reference processor to compare with. Line4 Check runs a check only once it is proven against the specification itself: Line4 wrote out how the specification says each kind of check runs, built test files so that every check passes on one file and fails on another, and ran every check on every test file. Line4's engines and a separate reading of the specification give the same result every time.

For the three forms that is 136 test files and 193,832 results, with no difference. As a second test, the checks were also run on the 4,297 Call Reports in the CDR's public bulk data for June 30, 2026, with that quarter's edits. Line4 Check is a prototype of the Line4 validation engine, not certified software.

How it works

  1. 01Your browser downloads the engine and the editsThe Line4 engine with its XBRL-XML reader is compiled to WebAssembly (530 KB). Only the edits of your form are downloaded: the FFIEC 031’s are 266 KB. Your browser keeps them for next time.
  2. 02Your file is opened on your computerThe XBRL-XML instance is read inside the browser tab, in a background worker so the page stays responsive. Its schemaRef says which form and report date it is. Nothing is uploaded.
  3. 03The checks run and are listedEach failed check is listed by schedule, in the FFIEC’s own words, with the values your file reports and the FFIEC’s edit number. Download it all as a CSV.

Questions

Which reports can I check?

The Call Report for the September 30, 2026 report date, on any of its three forms: FFIEC 031 (banks with domestic and foreign offices), FFIEC 041 (banks with domestic offices only) and FFIEC 051 (smaller banks with domestic offices only). Choose the XBRL-XML file your Call Report software makes before you submit it to the CDR. Line4 Check reads the form from the file’s schemaRef and runs that form’s checks.

Is it free?

Yes: free, 10 checks a month, with no account and no upload. Line4’s test files do not count, and the count starts again on the 1st of each month. After a result you can leave your email address to get the report by email, if you want it.

Does my file leave my browser?

No. Your file never leaves your computer. Your browser downloads the Line4 engine (WebAssembly) and the FFIEC’s edits for your form from line4.ai, then opens and checks the file on your own computer. Nothing is uploaded, and nothing from the file is recorded. If you ask for the report by email, only the report you see is sent to Line4, not the file.

What do errors and warnings mean?

Errors are validity edits: the CDR rejects a report that fails one, so they must be fixed. Warnings are quality edits: the CDR accepts the report, but you must explain each one that fails. Sum checks are shown as warnings, not errors. The CDR’s specification treats them as exact, but the CDR has accepted filed reports whose sums are off by a rounding difference.

Why does a report I downloaded from the CDR fail?

A Call Report downloaded from the CDR’s public site always fails edit R0002.7523, because the public data leave out the vendor code that the edit checks. Your own file, from your Call Report software, carries it.

Why are some checks not run?

1,400 of the 5,596 checks that apply to the three forms, counted form by form, do not run yet: 1,267 needs last quarter’s report; 76 uses data the CDR works out itself; 38 sums the taxonomy defines two ways; 19 checks that cannot fail. Line4 Check never counts a check it does not run as passed, and every report says how many ran.

Is this the same as the CDR’s own edits?

No. It is a free check to catch problems before you submit. The edits the CDR runs when you submit decide whether your report is accepted, and the CDR also runs checks that need data this page does not have, such as last quarter’s report.

What does Line4 record?

For each check: the form checked and its report date, the file format, the kind of result (passed, warnings only, blocking errors, nothing could be checked, or a report not covered), the address of the page it ran on without anything after ? or #, and the time. Never the file or any part of it, its name, the bank or its RSSD ID, any value or message, or which or how many checks failed.

Sources