ACH Standard Entry Class code

BOC SEC code: Back Office Conversion Entry

Check presented in person and converted to a debit in the back office.

What BOC is for

A check handed over in person — at a store counter or a staffed bill-payment location — and converted to a one-time ACH debit later, in the back office.

The account the paper check is drawn on.

Authorization

The Originator posts notice where it accepts checks that they may be converted; handing over the check after that notice authorizes the debit. Only checks the Rules define as eligible items may be converted; check the eligibility list before converting.

A summary in general terms: the Nacha Operating Rules set the exact requirements, and Regulation E adds its own for consumer accounts.

Debits, credits and addenda

Debits only. A credit sent as BOC is returned R36.

Addenda on a forward entry: none on the forward entry. Returns (addenda type 99) and Notifications of Change (type 98) follow their own layouts whatever the SEC code.

Returns

As for ARC: R37 (check also presented, 60 days, written statement), R38 (stop payment on the check, 60 days) and R39 (ineligible or already-paid check, 2 banking days).

Common mix-ups

ARC, BOC and POP all turn a paper check into a one-time ACH debit. The difference is where the check was received: by mail or in a drop box (ARC), in person but converted later in the back office (BOC), or at the point of purchase, where the check is voided and handed back (POP).

Where BOC sits in a NACHA file

The SEC code is a batch-level field: positions 51–53 of the Company/Batch Header record (type 5), so every entry in the batch shares it, and a file that mixes SEC codes puts them in separate batches. The batch header also carries the Company Name, Company Identification and Company Entry Description that Receivers see on their statements.

To read a BOC batch record by record, open the file in NACHA Navigator, a free sister site that parses NACHA files in your browser without uploading them.

Look up BOC from code or an AI agent

REST · GET · no key

curl -s 'https://payopskit.com/api/v1/codes/BOC?set=ach-sec'

MCP · tools/call · lookup_payment_code

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "lookup_payment_code",
    "arguments": {
      "code": "BOC",
      "set": "ach-sec"
    }
  }
}

Response (JSON)

{
  "code": "BOC",
  "set": "ach-sec",
  "found": true,
  "matches": [
    {
      "set": "ach-sec",
      "code": "BOC",
      "name": "Back Office Conversion Entry",
      "description": "Check presented in person and converted to a debit in the back office.",
      "details": {
        "direction": "debit",
        "addendaTypes": null,
        "minAddenda": 0,
        "maxAddenda": 0
      }
    }
  ]
}

The MCP server is at /mcp (Streamable HTTP, no key); the API and MCP docs show how to connect Claude, Cursor or VS Code.

Source: Nacha Operating Rules, Appendix Three (Standard Entry Class codes). The code’s name is the Rules’ own; the rest is this site’s plain-language summary, informational and not a substitute for the Rules or your ODFI agreement.