Banking details and invoices

Instructions for Banking Details and Invoices

What the add-on does

The add-on collects customer or vendor requisites, saves organization details in the order, and generates an invoice for payment. It supports four counterparty types: legal entity, sole proprietor, individual, and self-employed customer.

Legal entities and sole proprietors can use DaData suggestions by TIN or company name. The invoice can be printed, downloaded as a PDF, and sent to the customer by email.

Where to find the add-on

• Add-ons → Manage add-ons → Banking Details and Invoices — general settings, invoice options, and field sets for each counterparty type.
• Administration → Payment methods — the payment method that uses the MS: Issue an invoice processor, recipient requisites, and stamp image.
• Orders → View orders — requisites in the order list and order details, plus actions for sending, printing, and downloading an invoice.
• My organizations in the customer account — saved organizations, when this option is enabled in the add-on settings.

Add-on settings

General section

• API key — the DaData API key used for suggestions and automatic filling by TIN or company name. If the key is empty, the fields remain available for manual entry.
• Display fields with details on the checkout page — shows the requisite fields at checkout.
• Display fields with details in the buyer's profile — adds requisites to the customer profile.
• Display fields with details in the seller's profile — adds requisites to the vendor profile in Multi-Vendor.
• Automatically fill in user fields — inserts previously entered customer requisites at checkout.
• Establishment and maintenance of organizations in the profile — adds the My organizations section, lets customers select a saved organization at checkout, and allows entered requisites to be saved. This section is available to signed-in customers.

Invoice section

• Send invoice by mail — automatically sends an invoice when the order receives status O. The message is sent to the email address stored in the order and contains a PDF attachment.
• Show invoice buttons on the thank you page — shows print and PDF download actions immediately after order placement.
• Show invoice buttons on order details page — shows the same actions in the customer's order details.
• Open in new window — opens the printable invoice in a new browser tab from the storefront order details page.

Browser printing is available without an additional add-on. PDF generation and automatic PDF attachments require the PDF Documents add-on to be operational.

Fields for counterparty types

Separate setting sections are provided for legal entities, sole proprietors, individuals, and self-employed customers. They control company name, personal name, TIN, OGRN or OGRNIP, KPP, addresses, bank details, passport and registration data, phone, and email. The available fields differ by counterparty type.

Each field has the following options:

• Use — enables the field for the selected counterparty type.
• Show at registration — shows the field in the registration or profile form where the add-on adds requisites.
• Show at checkout — requests the field in the checkout requisite block.
• Show in invoice — includes the completed value in the customer or recipient details on the invoice.
• Required — prevents the corresponding form from being submitted without a value.

Make a field required only when it is also shown in the relevant form. After changing field sets, test every counterparty type used by the store.

Other settings section

• Automatic company name filling — when a vendor registers, copies either the person's full name or the legal entity name to the standard Company field. Select Do not use to disable copying.
• Use fields — controls which counterparty types are available in the selector: legal entities, sole proprietors, individuals, and self-employed customers.
• Display organization requisites in orders — shows a compact block with company name, TIN, phone, and email in the order list and order details.

Payment method and recipient requisites

1. Open Administration → Payment methods and create or edit the payment method used for invoicing.
2. On the processor settings tab, select MS: Issue an invoice.
3. Enter the recipient's counterparty type, name, TIN, registration and bank details, address, director, and chief accountant. The invoice includes completed fields that are allowed by the Show in invoice option for the corresponding counterparty type.
4. If needed, upload a stamp image and set its size and position.
5. Save the payment method and make sure it is available to the required storefronts and user groups.

The recipient name, TIN, checking account, bank name, BIK, and correspondent account are especially important for the invoice. Before using the payment method, check the printable form: it includes recipient requisites, customer requisites, ordered products, shipping, taxes, and the total.

Stamp image parameters

• Stamp image — the image placed next to the director and chief accountant signatures on the invoice.
• Stamp image width (image_stamp_width) — image width in pixels. The default value is 120.
• Stamp image height (image_stamp_height) — image height in pixels. The default value is 120.
• Left position for stamp image (image_stamp_left) — horizontal image offset in pixels. The default value is 130; increasing it moves the stamp to the right.
• Top position for stamp image (image_stamp_top) — vertical image offset in pixels. The default value is -20; a negative value moves the stamp upward.

After changing the size or offsets, check both the printable version and the PDF because browser printing and PDF rendering may differ slightly.

Checkout flow

1. The customer chooses to place the order as an organization and selects a counterparty type.
2. The customer selects a saved organization or enters requisites manually. When a DaData API key is configured, supported fields can be filled from suggestions by TIN or company name.
3. After the customer selects MS: Issue an invoice and places the order, the add-on saves the requisites in the order and assigns status O.
4. The customer prints or downloads the invoice from an available order page. If automatic sending is enabled, the PDF invoice is also emailed to the address stored in the order.

Statuses, payment confirmation, and payment-flow limitations

MS: Issue an invoice generates an invoice; it is not a bank or payment gateway integration and does not send a payment request to an external service.

• Order status: the processor assigns status O when the order is placed. The add-on does not check whether funds reached the bank account, so an administrator must update the order status manually or through another integration after payment.
• Test mode: not available because the add-on does not connect to a payment gateway. Test it by placing an order and reviewing the generated invoice.
• Hold, capture, and void: not supported. The add-on neither authorizes nor captures funds.
• Receipts, fiscalization, and DigitalKassa: the add-on generates a payment invoice, not a fiscal receipt or online cash-register data. It has no dedicated fiscalization settings.

Merchant ID

The add-on has no Merchant ID or merchant_id setting: a merchant identifier is not required because the add-on does not create a payment in an external gateway. A payment service Client ID and API token are not required either. The API key setting belongs only to DaData and is used for requisite suggestions; it does not participate in issuing or confirming a payment.

Webhook

No webhook is configured for this add-on. The payment method has no webhook URL or callback URL field, and the processor is declared without callback handling, so it does not accept bank notifications. An external service therefore cannot use this add-on to confirm payment or update the order status automatically: receipt of funds and the resulting status must be checked and recorded manually or by a separate integration.

Refunds

The add-on does not create refund operations or send refund requests to a bank; the order details and payment method settings provide no such action. Refund a bank transfer outside the add-on according to the store's and bank's procedures. After the refund, an administrator must manually align the order status and order data in CS-Cart with the actual transaction.

Invoice actions in the administration panel

The following actions are available in the details of an order placed with the MS: Issue an invoice processor:

• Send — generates a PDF and sends it to the email address stored in the order.
• Invoice for payment — opens the printable invoice.
• Invoice for payment (PDF) — generates and downloads the PDF.

These actions do not generate this add-on's invoice for an order placed with another payment method.

How to check the result

1. Leave only the required counterparty types and fields enabled at checkout; define clear requirements for fields made mandatory during testing.
2. If DaData suggestions are needed, enter the API key and test a search by TIN or company name. Repeat the test without a suggestion to verify that manual entry remains available.
3. Configure a payment method with the MS: Issue an invoice processor, fill in the recipient requisites, and upload a stamp image.
4. Place a test order for every counterparty type used by the store. Check required fields, organization saving, and reuse from My organizations.
5. Make sure the order received status O and that the customer requisites are visible in the order details.
6. Compare the printable version and PDF. Requisites of both parties, products, shipping, taxes, total, and stamp must be displayed correctly.
7. Test manual and automatic invoice sending to a real test email address. If PDF generation fails, first check that the PDF Documents add-on is available.
8. After simulating payment, verify that the order status does not change automatically. Manual payment confirmation is expected for this processor.