Banking information
Overview
Banking information stores the bank account your team cites on financial bid forms β bank name, branch address, IBAN, and SWIFT/BIC. Complete this section before creating your first pursuit, together with Company profile and Legal representative, so auto-fill and generated documents include correct payment details from the start.
Banking data is static in Tendersight. It does not connect to live banking APIs or verify accounts β you enter values exactly as they appear on your bank letter or official stationery.
Tip: Before you save, confirm:
IBAN matches your bank confirmation letter (every character)
SWIFT/BIC is correct for cross-border forms
Bank name and address match what authorities expect on guarantee forms
You are editing the correct active team if you manage multiple entities
Important: Banking is one of three sections required for team settings complete on Team overview. Missing banking triggers document filler warnings and placeholder text on financial PDFs.
Where to find it
Open Team β Management β Settings. Banking information is the fourth section in the grid (after company profile and company logo).
Subtitle: "Information regarding the banking arrangements put in place for this team."
Read view layout
Standard cog + clickable rows pattern shared with company profile and legal representative.
Header:
Gear icon (top-left) β opens edit sheet
Section title and subtitle
Vertical list with primary-colored left border
Two ways to open the edit sheet: click the cog icon, or click any row. Rows highlight on hover. Enter or Space on a focused row also opens the sheet.
What each row shows
Edit sheet
Title: Update banking information
Description: "Make changes to your team's banking information here. Click save when you're done."
Fields
Fill every field your tender procedures require. EU procurement forms typically need IBAN and SWIFT together.
Footer actions
After saving
Read view refreshes immediately on success.
Loading and error states
Cog and rows stay hidden until load succeeds.
Where banking data is used

Without banking information, the document filler warns that team settings are incomplete and may skip bank-related fields β leaving blanks or "complete" placeholders.
Banking vs company profile
Authorities often cross-check that the account belongs to the legal entity named in company profile β keep both aligned.
Workflow: first-time setup
Open Team β Settings
Complete Company profile
Open Banking information (cog or any row)
Enter bank name, address, IBAN, SWIFT from official bank letter
Save changes
Complete Legal representative
Verify overview checklist clears Configure team settings
Safe to create your first pursuit
Workflow: account change mid-season
Obtain new bank confirmation letter
Update banking sheet before next submission deadline
Regenerate financial forms and offers in open pursuits β old PDFs keep old IBAN
Permissions
Edge cases
What you cannot do
Connect live bank feeds or balance checks
Store multiple IBANs per team in this section
Validate IBAN checksum in the UI (enter carefully)
Set pursuit-specific bank accounts here
Best practices
Copy IBAN from bank PDF β avoid manual retyping
Update before guarantee or payment annex regeneration
Match currency and account rules in the tender (RON vs EUR accounts)
Complete banking in the same session as profile and legal rep
FAQ
Must I fill every field?
Fill every field your procedures require. IBAN and SWIFT are needed on most EU financial forms.
Can I edit one field only?
The sheet always shows all four fields. Change what you need; save once.
Does this connect to my bank?
No. Static details for document generation only.
Does saving empty banking complete the checklist?
Technically if saved once, but forms will still lack data β fill real values.
Troubleshooting
Related articles
Team settings
Company profile
Legal representative
How information flows
First pursuit workflow