Business Rules and Processing Conditions

Business rules are the conditions that decide how a payment is processed, and in payments they are numerous, precise and often invisible until one of them is broken. A cut-off time rule decides whether a payment is processed today or tomorrow. A value dating rule decides which date the beneficiary's account is credited. A charge rule decides who pays the fees and how much. A validation rule decides whether a payment is accepted or rejected. The analyst's job is to find every rule, write it down in plain language, and make sure the system enforces it exactly. Cut-off times are the most common source of customer complaints, so they must be documented with complete precision. A rule might state that outward remittances received before 3 in the afternoon Indian Standard Time are processed the same day, while those received after 3 in the afternoon are processed the next working day. The rule must also say what counts as received, whether it is the moment the customer submits the instruction or the moment it passes validation, and what happens on a bank holiday. A payment submitted at five past 3 in the afternoon on a Friday before a Monday holiday is value dated Tuesday, and the customer must be told that at the point of submission. Value dating rules determine the date from which interest is calculated on the payment. For a domestic transfer the value date is usually the same as the processing date, but for a cross-border payment it depends on the currency, the destination and the correspondent bank's calendar. A US dollar payment sent from Mumbai to New York on a Friday is typically value dated Monday, because Saturday and Sunday are not business days in the United States. The analyst documents these rules in a table by currency and corridor, because a developer cannot derive them from a single sentence. Charge rules decide who bears the cost of a payment and how the charge is calculated. In SWIFT payments the field 71A carries the charge code. OUR means the sender pays all charges, BEN means the beneficiary pays them, and SHA means the charges are shared. A bank might charge a flat 500 rupees for an outward remittance up to 100,000 rupees and 0.1 percent above that, with a minimum of 750 rupees. The rule table must state the charge for every band, the currency of the charge, and whether the charge is deducted from the payment amount or debited separately. Validation rules are the checks a payment must pass before it is released, and each one needs an exact error message. A validation might require that the beneficiary account number is exactly 34 characters for an IBAN, that the amount is greater than zero and not more than 10,000,000 rupees, and that the purpose code is one of the approved values such as P0101 for export of goods. If a rule fails, the system must reject the payment with a clear message such as beneficiary account number is not a valid IBAN, rather than a generic error, so that operations can fix the problem without guessing. The rule table is the analyst's main tool for documenting all of this. Each row has a rule identifier such as BR-001, a plain language description, the condition that triggers it, the action the system must take, and the source of the rule, which might be a central bank regulation, an internal policy or a scheme rule. The table is reviewed with business, operations and compliance, and every row is signed off. When a rule changes, the table is updated and versioned, so the team always works from one agreed source of truth.