About: Real-time posting     Goto   Sponge   NotDistinct   Permalink

An Entity of Type : owl:Thing, within Data Space : dbpedia.demo.openlinksw.com associated with source document(s)
QRcode icon
http://dbpedia.demo.openlinksw.com/describe/?url=http%3A%2F%2Fdbpedia.org%2Fresource%2FReal-time_posting&invfp=IFP_OFF&sas=SAME_AS_OFF

Real-time posting refers to a style of processing financial transactions in a core banking system. It is an alternative to the older Memo Posting style. There are several characteristics that distinguish a real-time posting system. Sometimes real-time posting is thought to mean 'there is no batch'. This is not the case. Real-time posting systems still need to support batch processing. Batch processing is attractive for some processing as it is a cost-effective means to process large groups of items. Examples of those batches would be check (cheque) clearing files or payment exchange files.

AttributesValues
rdfs:label
  • Real-time posting (en)
rdfs:comment
  • Real-time posting refers to a style of processing financial transactions in a core banking system. It is an alternative to the older Memo Posting style. There are several characteristics that distinguish a real-time posting system. Sometimes real-time posting is thought to mean 'there is no batch'. This is not the case. Real-time posting systems still need to support batch processing. Batch processing is attractive for some processing as it is a cost-effective means to process large groups of items. Examples of those batches would be check (cheque) clearing files or payment exchange files. (en)
dcterms:subject
Wikipage page ID
Wikipage revision ID
Link from a Wikipage to another Wikipage
sameAs
dbp:wikiPageUsesTemplate
has abstract
  • Real-time posting refers to a style of processing financial transactions in a core banking system. It is an alternative to the older Memo Posting style. There are several characteristics that distinguish a real-time posting system. 1. * Transactions appear to customers and staff as soon as the item is posted and does not need to be re-processed at night to create the hard post. 2. * The available balances are always up-to-date with respect to all known items. 3. * The order of posted items does not change as may sometimes happen in memo-post systems when the memos are deleted and re-processed. 4. * Memo-posting systems often need to go off-line while the database is re-loaded to prepare for the next day's business. Real-time systems do not need that re-load window. Sometimes real-time posting is thought to mean 'there is no batch'. This is not the case. Real-time posting systems still need to support batch processing. Batch processing is attractive for some processing as it is a cost-effective means to process large groups of items. Examples of those batches would be check (cheque) clearing files or payment exchange files. Many banking systems that implement real-time posting are also built on top of database management systems which allows for the banking system to be more available, even continuously available. The database foundation also allows for multiple batch processes to occur concurrently with more flexibility than can be easily achieved with traditional memo-post systems. Also, the database allows concurrent batch and online processing. This doesn't mean that a database couldn't be used at the core of a memo-post systems, but it would not be commonly done. (en)
prov:wasDerivedFrom
page length (characters) of wiki page
foaf:isPrimaryTopicOf
is Link from a Wikipage to another Wikipage of
is Wikipage redirect of
is foaf:primaryTopic of
Faceted Search & Find service v1.17_git139 as of Feb 29 2024


Alternative Linked Data Documents: ODE     Content Formats:   [cxml] [csv]     RDF   [text] [turtle] [ld+json] [rdf+json] [rdf+xml]     ODATA   [atom+xml] [odata+json]     Microdata   [microdata+json] [html]    About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data] Valid XHTML + RDFa
OpenLink Virtuoso version 08.03.3330 as of Mar 19 2024, on Linux (x86_64-generic-linux-glibc212), Single-Server Edition (378 GB total memory, 58 GB memory in use)
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2024 OpenLink Software