Secure file storage
The BankFabric application stores in/outbound bank files in Azure “blob” storage. These files are encrypted at rest within the storage container. Sensitive banking files (in- or outbound) should never be presented to the end user for modification and/or viewing. By user, within the BankFabric interface, location folders and file access permissions can be configured. See BankFabric security page.
Secure, seamless, automated bank communications
SFTP configurations are all configured and managed within BankFabric. With these bank settings configured within the ERP, all file transports are seamless and in real-time. Built-in PGP encryption and signing is available when required.
API based bank communications
seamlessly transmit payment files (and responses) and bank transactions through BankFabric’s API supported interfaces (starting with TAS v11.7)
Many of the Treasury Automation Suite processes can be run in an unattended mode, by leveraging the D365F&O batch job system. BankFabric is the platform used to execute these unattended tasks.
Multi-environment file overwrite protection
“Sandbox” databases are frequently refreshed from production environments. The downside of this is that the in/outbound file paths will still be pointing to the production locations on the sandbox db. BankFabric prevents this type of contamination across environments. It uses both the environment DNS and a unique encrypted “secret” to verify the appropriate ERP environment is communicating value with corresponding
File locations and names are configured within BankFabric and visible in the ERP. Locations are automatically maintained across all environments.
Simplified filename and location setup
All UI and API calls are logged and available for review by the account administrator and/or SKG personnel.