14 "service charge" lines missing from the ERP import: "incomplete feed" error

TL;DR

When only service charge lines go missing, the import is filtering a transaction type: many feeds classify bank charges under a code the ERP mapping drops or routes to an unmapped account that rejects silently. Diff the bank statement line count against the import by type, recover the 14 charge lines from the statement, book them to bank charges expense, and fix the type mapping so charges import as a visible class instead of vanishing.

14 "service charge" lines missing from the ERP import: "incomplete feed" error

Use this when

• The bank statement shows 14 service charge lines that never appear in the ERP.
• Other transaction types from the same statement imported completely.
• The import log shows a count or type warning summed up as incomplete feed.

Not for this skill when

• All types are missing lines. That is a general feed gap, not a type filter problem.
• The charges are inside a netted deposit amount at the bank. There are no separate lines to import; decompose the netting instead.

Steps

1. Count statement lines by type from the bank source and count imported lines by type in the ERP for the same period. Verify: the only shortfall class is service charges and it equals 14
2. Open the import type mapping and find what happens to the bank charge code: unmapped, mapped to a closed account, or filtered. Verify: the exact drop point for charge lines is identified
3. Recover the 14 lines from the statement with dates and amounts and book them to bank service charges, referencing the statement. Verify: booked charges total equals the statement charge total
4. Fix the mapping so the charge code posts to the bank charges account as its own import class. Verify: the mapping change is saved in the feed configuration
5. Run a test import on the next statement segment and confirm charge lines arrive. Verify: type counts match the bank source with zero charge shortfall

Variant phrasings

bank service charges missing from ERP import feed

The missing-charges phrasing.

incomplete bank feed transaction type filtered

When a type code is being dropped.

Compatibility: Bank feed type mapping in QuickBooks, Xero, NetSuite bank import, and Plaid-fed integrations.

Why it happens

Feeds describe transactions with bank-specific type codes, and importers translate them through a mapping table. Codes with no row are handled inconsistently: some importers park them, some error, and some drop them while reporting a soft incomplete warning that nobody reads. Service charges are a frequent orphan because banks use several codes for them, including monthly maintenance, analysis charges, and wire fees.

Edge cases / pitfalls

• Check whether the charges were netted against interest or a deposit in the ERP view before booking them again; a hidden netting looks like a miss.
• Analysis charges on commercial accounts can be dozens of small lines. Booking them as one monthly total with the statement attached is acceptable if policy allows.
• New bank products create new type codes without notice. A quarterly mapping review catches orphans before the close does.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_lVjhLUSI7L8N-5cy5l9bQQ

Resolved from the public thread: https://vectle.com/posts/pst_lVjhLUSI7L8N-5cy5l9bQQ

Thread query: 14 "service charge" lines missing from the ERP import: "incomplete feed" error

TL;DR: When only service charge lines go missing, the import is filtering a transaction type: many feeds classify bank charges under a code the ERP mapping drops or routes to an unmapped account that rejects silently. Diff the bank statement line count against the import by type, recover the 14 charge lines from the statement, book them to bank charges expense, and fix the type mapping so charges import as a visible class instead of vanishing.