Interacts with Bankgirot and generates and parses related files.
Uses the Bankgiro Link web service to send and receive supplier/customer payment orders and to handle automatic transaction assignments (Autogiro) as well as electronic invoices.
For "BankID Security Application" installation instructions, see https://install.bankid.com/.
For bankgiro and plusgiro columns, the component will strip the characters '.', '-', and ' '. All other non-numeric characters will result in an error. The resulting number must contain 10 digits or less.
Bank account numbers should start with the clearing number (four digits) followed by the account number. For clearing numbers with five digits (Swedbank), do not include the fifth digit.
The button for Mobile BankID will only be enabled if the current user's personal number has been registered with SoftadminApi.User_UpdatePersonalNumber.
For a list of banks supporting Mobile BankID, see the table at the end of the Bankgiro Link Overview. Even if a bank is listed as supporting Mobile BankID, it might not support all file types and operations. The only way to know for sure is to contact the bank directly.
Files are signed by the current user with BankID when they are uploaded.
SQL to retrieve what kind of files are being transferred or files already download that should be processed now.
Possible value | Description |
---|---|
AG | Triggers call AGMEDGIVKONF, AGMEDGIVANM, AGBETRED, or AGBETMAKRED depending on file contents. |
BGI | Triggers call BGI. |
FHO | Triggers call FHO, EFA, or EFMEDGIVANM depending on file contents. |
LBUT | Triggers call LBUT. |
SQL to tell the component which files have already been downloaded. Files older than 30 days will never be downloaded. If resultset is empty all files will be fetched.
SQL with rows corresponding to supplier payments. Is used to send LBIN files to Bankgirot.
Possible value | Description |
---|---|
SEK | Specifies Swedish Krona as the currency for the transaction. |
Possible value | Description |
---|---|
14 | Payment |
16 | Credit invoice |
17 | Credit invoice, whole amounts |
Is used to send AGMEDGIVREG files to Bankgirot. SQL with rows corresponding to payers whose admission, to be eligible for automatic transactions, should be registered or withdrawn. Accounts must be registered with AGMEDGIVREG before automatic transactions can be set up using AGBETUND.
Is used to send AGBETUND files to Bankgirot. SQL returning details for automatic transaction initiation. Payers must have been registered for automatic transactions by means of AGMEDGIVREG previously.
Possible value | Description |
---|---|
FULLYEAR | Transaction occurs yearly. |
HALFYEAR | Transaction occurs every half year. |
MONTH | Transaction occurs monthly. |
ONCE | Transaction occurs only once. |
QUARTER | Transaction occurs quarterly. |
Is used to send AGBETMAK files to Bankgirot. SQL returning identification info for assignment to be withdrawn. Withdrawal will be effective for all assigments corresponding to a combination of payer number and BankgiroTo number. Only revokes the assignments from AGBETUND, not the admission through AGMEDGIVREG.
The following combinations are available for cancellations:
PayerNumber
The above + DueDate
The above + Amount
The above + Reference
The following combinations are available for amendments:
NewDueDate
The above + DueDate
The above + PayerNumber
The above + Amount
The above + Reference
Recurring payments can not be amended.
Is used to send BGC INVOICE files to Bankgirot.
The call is only made if the EF column is set in the 'Get Actions' database call.
Possible value | Description |
---|---|
AAB | Ålandsbanken |
FINN | Sparbanken Öresund |
FSPA | Swedbank |
ICA | ICA banken |
LFB | Länsförsäk.bank |
NB | Nordea |
OEB | Danske Bank |
SBAB | SBAB |
SEB | SEB |
SHB | Handelsbanken |
SKB | Skandiabanken |
SYD | Sparbanken Syd |
SQL to save the finished generated file and is called after the file has been sent to Bankgirot. A Success report is included in the call. It is used with "LBIN", "AGMEDGIVREG", "AGBETUND", "AGBETMAK", or "EF".
Possible value | Description |
---|---|
AGBETMAK | Withdraw autogiro assignment. |
AGBETUND | Autogiro assignment. |
AGMEDGIVREG | Autogiro admission. |
EF | eInvoice |
LBIN | Supplier payment |
This call is made once for each file in the "Files to approve" result set of the "Get actions" call.
SQL for saving downloaded files to database. N.b. Bgc_FileId should be stored in database for future use.
Possible value | Description |
---|---|
AG | |
BGI | |
LBUT | |
OTHER |
SQL with details of supplier payments. Is only used with LBUT.
SQL with details of customer payments. Is only used with BGI.
SQL to save confirmations of automatic transaction admission registration or withdrawal.
Possible value | Description |
---|---|
BANK | |
PAYER | |
RECEIVER | |
SENDER |
SQL to save electronic annoucements of admissions for automatic transactions.
SQL to save reports of success or failure of automatic transactions.
May also include refund information. This only applies to New Autogiro files.
SQL to save reports of success or failure for withdrawal of automatic transaction assignments.
Fakturautställaren kan definiera egna fält för anmälningsärenden. Temptabellen #Fields(Name char(3), Value varchar(max)) innehåller de fält som fyllts i av fakturamottagaren.
Possible value | Description |
---|---|
0 | Production. |
1 | Registrations were sent for testing. |
SQL to report when file has been parsed with correct action.
Starting with version 7.8.001: Both this call and the "Finished" call use the @Finished parameter, but only this call will include @BankFileId.
This call is made after all other calls have been made.
Both this call and the "File successfully parsed" call use the @Finished parameter, but only "File successfully parsed" will include @BankFileId.
Allows you to validate the SQL parameters before any other SQL is run in the component. This call is only made if the SQL is a stored procedure and Validate parameters is checked.
Use this call to restrict which entries a user is allowed to view and edit, and to log which entries a user views.
Access to a menu item is normally controlled through functions and roles alone but some entities need more fine grained control. For example, a user may have access to the View Member menu item for normal members but not for members with a protected identity.
The menu items a user visits are always logged (in ADMINLogMenuItem) but for sensitive data you may need to log exactly what entries are viewed. Do the logging in this call as the common ways of viewing data (grid and InfoSQL) are not allowed to modify the database.
If you bind a scalar function instead of a stored procedure to this call then its name must end with '_GrantAccess'.