A convention that counts actual days in the period divided by 360, commonly used in financial markets for interest calculations.
The Actual/360 day count convention is a financial standard used to calculate interest payments on various financial instruments such as bonds, loans, and derivatives. This method divides the actual number of days in an interest calculation period by 360.
The Actual/360 method computes interest by taking the exact number of days in the period (the actual) and dividing it by 360. This often results in higher interest payments compared to methods using a 365-day year.
The Actual/360 convention is vital for:
For finance readers, Actual/360 is useful when reviewing funding, deposits, lending margins, payment flow, liquidity, and bank operational controls. Actual/360 connects the definition to measurement, timing, risk, documentation, and comparability decisions instead of leaving the concept as isolated vocabulary.
If Actual/360 appears in an analysis file, compare the stated amount, rate, right, or obligation with the supporting contract, account, market data, or policy. Then identify how Actual/360 changes who benefits, who bears the risk, and which financial statement, valuation, or cash-flow line changes.
Ask whether Actual/360 changes amount, timing, probability, liquidity, rights, reporting, or control evidence. If it does not, keep Actual/360 as context; if it does, tie it to the recommendation, valuation input, control step, disclosure, or risk decision.
Interpret Actual/360 through the bank’s role as intermediary: accepting funds, making payments, extending credit, managing risk, and reporting to supervisors.
In finance, Actual/360 matters when it affects liquidity management, interest margin, payment reliability, credit exposure, customer balances, or regulatory compliance.
Do not confuse Actual/360 with a generic banking service. The finance meaning depends on the account, balance-sheet effect, settlement step, or supervisory rule involved.
You will see Actual/360 in bank policies, account agreements, treasury reports, liquidity dashboards, regulatory filings, payment files, and operational-risk reviews.
Treat Actual/360 as material when it changes funding quality, cash availability, customer obligations, bank risk, or required controls.
Use Actual/360 when a banking decision depends on account treatment, deposits, funding, liquidity, customer rights, payment finality, controls, or regulatory treatment. The practical issue is whether cash can be considered available, restricted, stable, insured, pledged, or exposed to operational risk.
A useful review connects the term to three checks: the account or transaction record, the institution’s legal or operational obligation, and the finance consequence for liquidity, capital, fees, or reconciliation. If it changes funds availability, reserve needs, exception handling, customer disclosure, or balance-sheet presentation, handle it as a control and treasury issue, not just a service description.
For Actual/360, the decision impact is whether a bank or customer changes account treatment, funds availability, fee assessment, liquidity planning, reconciliation, customer communication, or compliance handling. If balances, rights, and controls are unchanged, Actual/360 is operational context.
Verify Actual/360 against the account agreement, ledger record, transaction log, fee schedule, exception report, availability rule, and control evidence. Actual/360 matters when cash availability, customer rights, liquidity, reconciliation, or compliance treatment changes.
Trace Actual/360 from account record to balance availability, authorization, fee treatment, reconciliation, exception handling, and compliance evidence. Actual/360 matters when it changes cash access, customer rights, funding treatment, operational risk, or the proof a bank needs before release or settlement.
The use boundary for Actual/360 is reached when account rights, balance availability, authorization, fees, reconciliation, exception handling, liquidity reporting, and compliance evidence are unchanged. In that case, keep the term operational and do not alter funds-release or control conclusions.
The decision marker for Actual/360 is the moment bank operations change: funds availability, authorization, balance treatment, fees, reconciliation, exception handling, liquidity reporting, or compliance proof. If operations are unchanged, keep the term descriptive.
The risk check for Actual/360 is whether operational language hides funds-availability or control risk. Test authorization, balance status, holds, fees, reconciliation, exception handling, fraud exposure, compliance evidence, and whether the bank can prove the treatment applied.
Decision evidence for Actual/360 should show account authority, ledger status, transaction record, fee treatment, reconciliation, exception owner, and compliance proof. Actual/360 can change banking analysis only when those facts alter funds availability, control, or liquidity treatment.
Review evidence for Actual/360 should make the banking evidence traceable, not just definitional. For Actual/360, tie the evidence to the account record, transaction log, customer authority, and ledger reconciliation and explain why that evidence is reliable enough for the finance decision.
Before relying on Actual/360, document the decision context: the processing date, value date, settlement window, and funds-availability rule. Keep the Actual/360 evidence trail visible: exception ownership, approval status, compliance evidence, and any operational limit that applies. In Banking work, Actual/360 matters when it changes liquidity, payment risk, account control, fee treatment, or balance reporting.
The practical risk for Actual/360 is that operational labels can hide timing, authorization, and reconciliation problems unless evidence is kept with the analysis. If those facts are unavailable, keep Actual/360 in the explanatory layer instead of treating it as decision-grade evidence.
Use this checklist before treating Actual/360 as a decision-ready input rather than background context:
If any checklist item is missing, keep the discussion descriptive; do not treat Actual/360 as final support for pricing, credit, valuation, reporting, tax, compliance, or portfolio decisions. This matters when the same label appears in contracts, statements, market data, and internal models with slightly different meanings.