Certinia Integration

the certinia integration provides base functionality that can be built upon and customised with salesforce standard tools certinia integration allows users to automatically collect invoices and subscription payments by pulling payments from the bank accounts of their customers around the world without ever leaving certinia how it works sales invoice posted in certinia a user posts a sales invoice in certinia, which triggers the integration asperato payment record & payment option created the integration automatically creates a payment record in asperato linked to the invoice and determines the payment method automated payment (if saved authorisation exists) or pay now link (if no authorisation) sets up for automatic collection or adds a payment link to the invoice customer payment and asperato record update after the customer payment, asperato updates the payment record status to collected from customer cash entry created and matched in certinia (if enabled) if automatic cash matching is configured, the integration creates a cash entry in certinia and matches it to the sales invoice, reflecting the payment payment process complete the invoice is considered paid, and the accounting process is updated in certinia if automatic cash entry is disabled, manual cash entry is required in certinia to see the integration in action, watch demo invoice collections for certinia https //asperato relayto com/e/demo invoice collections for certinia r3pu1234g46w5?doc hub=certinia asperato 64f713fb883b5\&hub=certinia asperato 64f713fb883b5\&hub nav=sidebar prerequisites to run the asperato payment process, a dedicated user with a certinia accounting licence, administrator permissions and access to all companies must be used in a multi company org this user must have all companies selected when running the asperato payments process to be eligible for payment processing using the integration, a payment integration method must be created with the ‘provider’ set to asperato and linked to the account in salesforce in a multi company scenario, there is a need to map the certinia bank account to the appropriate asperato customer id/merchant group in a multi company scenario, it is necessary to make a decision on where it makes sense to set the certinia bank account, this can be done at 3 levels (1) certinia company level; (2) on the payment integration method; (3) on a sales invoice or billing document recommended package versions the following table contains recommended package versions for certinia and certinia asperato connector, along with corresponding asperato versions, across various releases certinia certinia asperato connector asperato fall 2018 spring 2021 (no ffa summer 2021 release) summer 2019 sp3 v2 10, v2 11, v2 14 v2 16 fall 2021 fall 2021 2 17 1 (winter 22) spring 2022 spring 2022 2 18 1 (spring 22) summer 2022 summer 2022 2 19 1 (summer 22) winter 2023 winter 2023 sp1 v2 20 4 (winter 23) spring 2023 spring 2023 sp2 2 22 4 (summer 23) summer 2023 ffa summer 2023 sp12 / asp connector summer 23 sp4 2 22 4 (summer 23) winter 2024 winter 2024 2 23 5 (winter 24) spring 2024 winter 2024 sp2 2 23 5 (winter 24) summer 2024 winter 2024 v2 27 4 (summer 24) winter 2025 winter 2024 v2 27 4 (summer 24) spring 25 spring 25 2 31 (spring 25) integration 1\ install the asperato package for certinia integration, you must have installed and configured the asperato package see production installation docid\ ycedxo7v sa30ofjgzuk3 2\ install the integration package after installing asperato, raise a certinia support ticket to install the certinia asperato integration package for more information, visit certinia's documentation for setting up asperato connector 3\ configure the certinia asperato integration this involves setting up the integration to meet your specific business needs this includes auto generation of asperato payment records when sales invoices are posted in certinia cash matching payments collected through asperato to sales invoices/billing documents in certinia mapping certinia bank accounts to asperato customer ids/merchant groups setting the certinia bank account at the appropriate level (company, payment integration method, or sales invoice/billing document) to this end, questions for consideration include what will drive creation of payments/authorisations? for users of the certinia asperato integration, payment creation will usually be driven by posting sales invoices / billing documents which salesforce objects will need to be linked/related to asperato payments and authorisations? are customer payment email receipts required? email receipt requirements vary by customer and as such are not provided as part of the asperato application some psps send receipts by default is multi currency a requirement? which salesforce automation tools will help with integrating asperato into your business processes?