Establishing secure connection…Loading editor…Preparing document…

Business BACS Document

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

BUSINESS BACS DOCUMENT

This Business BACS Document (the Agreement) is entered into between:

RECITALS

WHEREAS, Client desires to procure services from Service Provider and to permit payments to be made or received by automated bank transfer using the BACS system; and

WHEREAS, Service Provider represents that it is capable of providing the described services and of receiving and processing payments by BACS in accordance with applicable banking practice and this Agreement; and

WHEREAS, the parties wish to set forth the scope of services, payment terms, authorization for BACS transfer and the mutual obligations of the parties.

SCOPE OF WORK

PAYMENT TERMS

Amount Payable: £ payable in accordance with the schedule below. All amounts are exclusive of applicable taxes unless otherwise stated.

Payment Method: Payments shall be made by BACS credit transfer to Service Provider's nominated bank account in cleared funds by the due date set out in the invoice or payment schedule. Service Provider will provide bank details and a unique payment reference to Client.

BACS PAYMENT INSTRUCTIONS

By signing this Agreement, Client authorises the initiation of BACS credit transfers to the bank details provided above for the purpose of paying amounts due under this Agreement. Client further warrants that it is legally authorised to instruct its bank to make such payments.

Client authorises BACS payments in accordance with the terms set out in this Agreement.

TERM AND TERMINATION

This Agreement commences on and continues until unless earlier terminated in accordance with this section.

Either party may terminate this Agreement for convenience upon giving written notice to the other party with a minimum notice period of . Termination for cause may occur immediately where a party materially breaches any obligation of this Agreement and fails to remedy such breach within 14 days of written notice.

CONFIDENTIALITY

Each party shall maintain in strict confidence all Confidential Information received from the other party and shall not disclose such information to any third party except as required by law or with the prior written consent of the disclosing party. Confidential Information shall include business plans, financial information, pricing, customer lists and technical information. The obligations of confidentiality shall survive termination of this Agreement for a period of unless a longer period is required by applicable law.

GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of . The parties submit to the exclusive jurisdiction of the courts of that jurisdiction for the resolution of disputes.

ENTIRE AGREEMENT

This Agreement constitutes the entire agreement between the parties with respect to its subject matter and supersedes all prior negotiations, representations and agreements, whether written or oral. No amendment to this Agreement is effective unless made in writing and signed by duly authorised representatives of both parties.

REPRESENTATIONS AND WARRANTIES

Each party represents and warrants that it has the full corporate power and authority to enter into this Agreement, that the execution and delivery of this Agreement has been duly authorised, and that performance of its obligations will not violate any applicable law, order or agreement with a third party.

MISCELLANEOUS

Notices under this Agreement shall be in writing and delivered to the addresses set out at the beginning of this Agreement. If any provision of this Agreement is held to be invalid or unenforceable, the remaining provisions shall remain in full force and effect.

Client:

By:

Date:

Service Provider:

By:

Date:

Enter text✕

What the Business BACS Document Is and when it applies

A Business BACS Document is a written authorization used to initiate or receive automated bank transfers under the BACS clearing system; it records payee and payer bank details, authorization scope, and signing parties. Although BACS is a U.K. payment network, equivalent U.S. processes typically use ACH authorizations; the form documents bank account numbers, routing information (or sort code equivalents), and the signer’s consent to recurring or one‑time debits or credits. In U.S. contexts this document often functions like an ACH authorization and may be executed electronically consistent with ESIGN (15 U.S.C. ch. 96) and state UETA rules where applicable.

Why a clear Business BACS Document matters for payments

A precise authorization reduces payment delays, prevents misdirected transfers, and documents consent for audit and compliance. It clarifies banking details, payment frequency, and liability allocation while supporting record retention requirements for tax, audit, and regulatory review.

Why a clear Business BACS Document matters for payments

Typical users and teams that handle Business BACS Documents

Several internal and external roles routinely prepare, review, or sign these authorizations depending on workflow and industry.

  • Accounts payable and treasury teams managing outgoing vendor or payroll transfers.
  • Vendors and service providers submitting bank details to receive client payments.
  • Legal and compliance staff verifying authorization language and retention requirements.

Match the preparer and signer to internal controls and approval thresholds to reduce fraud and operational errors.

Who typically signs and approves this document

CFO

Chief financial officers or finance directors sign or approve high‑value or recurring authorizations and set policy for bank account changes. Their review ensures segregation of duties, appropriate approval thresholds, and alignment with treasury controls.

AP Lead

Accounts payable managers or AP leads complete payee details, attach supporting invoices or W‑9s, and coordinate bank‑detail verification. They maintain records needed for tax reporting and internal audit trails.

Security and compliance elements to include

Encryption: TLS 1.2/1.3 in transit
Data at rest: AES‑256 encrypted storage
Audit trail: Timestamped signing history
Regulatory standards: SOC 2 Type II available
Health data: HIPAA requires BAA
FDA compliance: 21 CFR Part 11 supported

Step-by-step: completing a Business BACS Document

Follow these four steps to prepare and finalize a compliant bank authorization.

  • 01
    Collect details: Record legal business name and legal bank account data.
  • 02
    Verify identity: Confirm signer authority and match IDs or corporate resolutions.
  • 03
    Sign and date: Obtain signatures with date and specify effective start.
  • 04
    Store records: Retain signed copy per retention policy and audit needs.

Configuring an electronic workflow for this document

Common settings balance signer convenience with authentication and audit requirements.

Field Configuration
Authentication method Email plus SMS code
Required attachments W‑9 or vendor onboarding docs
Signature placement Designated signature and date fields
Retention rule Automatic archival and access controls

Technical and integration considerations

Choose a platform that supports secure storage, audit trails, and common integrations used by finance teams.

  • Integrations: Salesforce, NetSuite, Google Workspace
  • File formats: PDF, DOCX, XLSX supported
  • Authentication: Email, SMS, KBA options

Ensure the chosen solution can export signed documents with tamper‑evident audit reports and supports any required BAAs or compliance addenda.

Typical electronic authorization flow

A concise sequence shows how documents move from preparation to archived record.

  • Upload document: Sender uploads the completed form to the eSign platform.
  • Place fields: Add signature, date, and data validation fields.
  • Authenticate signer: Choose email, SMS code, or KBA as required.
  • Archive copy: Store signed copy with audit trail and attachments.

Timelines and typical processing expectations

Understand effective dates, bank clearing windows, and recordkeeping deadlines to avoid interruptions.

Effective date:

Enter MM/DD/YYYY; controls when transfers begin.

Bank processing window:

ACH/BACS typically clears in 1–3 business days.

Update notice period:

Allow 1–2 business days for account changes to take effect.

Record retention baseline:

Keep records at least three years for tax audits.

Revocation notice:

Provide written revocation as specified, commonly 30 days.

Key milestones from setup to active transfers

A sequential view of the authorization lifecycle helps coordinate approvals and bank setup.

01

Draft and review

Prepare the authorization and obtain internal approvals before sending.

02

Signer authentication

Authenticate signer identity and collect signature with timestamped evidence.

03

Bank verification

Bank may micro‑verify or request confirmation; this can add days.

04

Active transfers

Once verified, recurring or one‑time transfers execute per schedule.

Core sections a professional Business BACS Document should include

Each section below reduces ambiguity and supports operational, audit, and legal needs.

Payor and Payee

Include full legal names, business entity types, and authorized contact details so parties are unambiguously identified for tax reporting and dispute resolution purposes.

Bank account details

Provide the bank name, full account number, and routing or sort code in the exact format used by the bank to avoid misrouting and facilitate automated verification checks.

Payment terms

Specify whether transfers are one‑time, recurring, their amount or calculation method, and the schedule or trigger events that authorize each transfer.

Authorization language

Clearly state the scope of consent, conditions for revocation, and who bears liability for returned or unauthorized transactions to support dispute handling and bank inquiries.

Signature block

Include printed name, title, signature line, and date; for businesses attach a corporate resolution or proof of signer authority when the signer is not an officer.

Compliance statements

Note applicable law, consumer disclosures required by ESIGN for consumer agreements, and references to BAAs or data handling obligations when protected health information is involved.

Common preparation and processing pitfalls to avoid

  • Entering incorrect routing or account numbers, which can result in returned payments and recovery delays.
  • Using informal signer titles or unsigned authorizations that lack clear evidence of authority to transact.
  • Failing to collect required tax or identity documentation such as W‑9s or corporate resolutions.
  • Neglecting ESIGN consumer disclosures when authorizations involve consumer banking accounts.

Consequences of incomplete or incorrect authorizations

Misdirected funds: Bank returns and recovery costs
Tax withholding risk: 24% backup withholding
Information return penalties: 1099 penalties per IRC §6721
HIPAA exposure: Civil fines if PHI mishandled
Contract disputes: Increased litigation and remediation costs
Reputational harm: Customer trust erosion

Typical eSignature vendor pricing and features

Compare entry pricing and core features relevant to signing bank authorizations; signNow is listed first per platform comparisons.

signNow DocuSign Adobe Sign PandaDoc HelloSign
Starting Price $8/user/mo $15/user/mo $14/user/mo $19/user/mo $15/user/mo
Free Trial 7-day free trial, no card No No Limited trial Limited trial
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes (BAA) Yes (BAA) Yes (BAA) No No

Frequently asked questions about Business BACS Documents

Answers address legality, signing methods, corrections, notarization, retention, and authentication concerns.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users